1. 技术文章
  2. Eclipse plugin Aptana errors on Mac OSX Lion

Eclipse plugin Aptana errors on Mac OSX Lion

由 我们两清 提交于 2019-12-06 04:40:25

I had this issue on a Windows 7 plugin install of Aptana.

For me, the resolution ended up being to uninstall EGit.

Hope the same works for you! For Git functionality, there are many separate tools (even though it would be nice to run everything through Eclipse).

Damian Dobroczyński

For me, the solution of this problem (Ubuntu 11.04, Exlipse Helios) was to replace two jars in plugin directory. I've replaced (manually, of course):

  • org.apache.httpcomponents.httpcore_4.0.1.jar
  • org.apache.httpcomponents.httpcore_4.1.0.v201101201700.jar

(as you can see it's a potential source of problems) with the only one:

org.apache.httpcomponents.httpcore_4.1.jar

which I found in httpcomponents-core-4.1-osgi-bin.tar.gz file at Apache Http Core site (search in "archives").

Maybe only deleting v. 4.0.1 would do, but I did not checked this solution. So far, so good.

It seems to me that this is not an "eclipse on Lion" issue: I see this with Eclipse Helios under Linux amd64 as well every time I open a HTML page in Eclipse - even if I use a text editor and NOT the Aptana HTML editor. Will try if uninstalling EGit fixes it...

(I hate to be practicing thread necromancy, but this problem is still... a problem.)

I'm getting the same error using Eclipse 4.2 SR1 with the latest Aptana plugin (v3.x?) on Mountain Lion and Java 1.6.0_37. One of my eclipse workspaces is affected, but I can switch to an empty workspace and get Eclipse to start.

The .metadata/.log didn't provide any useful information, but I found something interesting in eclipse/configuration/derby.log:

    ============= begin nested exception, level (1) ===========
java.sql.SQLException: Database 'aptanaDB' not found.
    at org.apache.derby.impl.jdbc.SQLExceptionFactory.getSQLException(Unknown Source)
    at org.apache.derby.impl.jdbc.SQLExceptionFactory40.wrapArgsForTransportAcrossDRDA(Unknown Source)
    at org.apache.derby.impl.jdbc.SQLExceptionFactory40.getSQLException(Unknown Source)
    at org.apache.derby.impl.jdbc.Util.newEmbedSQLException(Unknown Source)
    at org.apache.derby.impl.jdbc.Util.newEmbedSQLException(Unknown Source)
    at org.apache.derby.impl.jdbc.Util.generateCsSQLException(Unknown Source)
    at org.apache.derby.impl.jdbc.EmbedConnection.newSQLException(Unknown Source)
    at org.apache.derby.impl.jdbc.EmbedConnection.handleDBNotFound(Unknown Source)
    at org.apache.derby.impl.jdbc.EmbedConnection.<init>(Unknown Source)
    at org.apache.derby.impl.jdbc.EmbedConnection30.<init>(Unknown Source)
    at org.apache.derby.impl.jdbc.EmbedConnection40.<init>(Unknown Source)
    at org.apache.derby.jdbc.Driver40.getNewEmbedConnection(Unknown Source)
    at org.apache.derby.jdbc.InternalDriver.connect(Unknown Source)
    at org.apache.derby.jdbc.AutoloadedDriver.connect(Unknown Source)
    at java.sql.DriverManager.getConnection(DriverManager.java:579)
    at java.sql.DriverManager.getConnection(DriverManager.java:243)
    at com.aptana.usage.AptanaDB.shutdown(AptanaDB.java:156)
    at com.aptana.usage.UsagePlugin.stop(UsagePlugin.java:71)
    at org.eclipse.osgi.framework.internal.core.BundleContextImpl$2.run(BundleContextImpl.java:771)
    at java.security.AccessController.doPrivileged(Native Method)
    at org.eclipse.osgi.framework.internal.core.BundleContextImpl.stop(BundleContextImpl.java:764)
    at org.eclipse.osgi.framework.internal.core.BundleHost.stopWorker(BundleHost.java:510)
    at org.eclipse.osgi.framework.internal.core.AbstractBundle.suspend(AbstractBundle.java:566)
    at org.eclipse.osgi.framework.internal.core.Framework.suspendBundle(Framework.java:1206)
    at org.eclipse.osgi.framework.internal.core.StartLevelManager.decFWSL(StartLevelManager.java:592)
    at org.eclipse.osgi.framework.internal.core.StartLevelManager.doSetStartLevel(StartLevelManager.java:257)
    at org.eclipse.osgi.framework.internal.core.StartLevelManager.shutdown(StartLevelManager.java:215)
    at org.eclipse.osgi.framework.internal.core.InternalSystemBundle.suspend(InternalSystemBundle.java:284)
    at org.eclipse.osgi.framework.internal.core.Framework.shutdown(Framework.java:692)
    at org.eclipse.osgi.framework.internal.core.Framework.close(Framework.java:600)
    at org.eclipse.core.runtime.adaptor.EclipseStarter.shutdown(EclipseStarter.java:399)
    at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:199)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke(Method.java:601)
    at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:629)
    at org.eclipse.equinox.launcher.Main.basicRun(Main.java:584)
    at org.eclipse.equinox.launcher.Main.run(Main.java:1438)
============= end nested exception, level (1) ===========

I don't know what to do with this information, but perhaps it will help the Aptana team figure out what's going wrong.

标签
java
eclipse
eclipse-plugin
aptana
易学教程内所有资源均来自网络或用户发布的内容，如有违反法律规定的内容欢迎反馈！
该文章没有解决你所遇到的问题?点击提问,说说你的问题,让更多的人一起探讨吧!