eclipse3.3装一些插件出了问题,启动不了,只能在启动参数加-clean才能启动

错误日志如下:
!SESSION 2009-04-16 20:54:35.515 -----------------------------------------------
eclipse.buildId=M20080221-1800
java.version=1.6.0_05
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=zh_CN
Command-line arguments: -os win32 -ws win32 -arch x86

!ENTRY com.aptana.rdt.ui 4 0 2009-04-16 20:54:43.937
!MESSAGE
!STACK 0
org.osgi.framework.BundleException: The activator com.aptana.rdt.ui.AptanaRDTUIPlugin for bundle com.aptana.rdt.ui is invalid
at org.eclipse.osgi.framework.internal.core.AbstractBundle.loadBundleActivator(AbstractBundle.java:141)
at org.eclipse.osgi.framework.internal.core.BundleContextImpl.start(BundleContextImpl.java:970)
at org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java:346)
at org.eclipse.osgi.framework.internal.core.AbstractBundle.resume(AbstractBundle.java:350)
at org.eclipse.osgi.framework.internal.core.Framework.resumeBundle(Framework.java:1118)
at org.eclipse.osgi.framework.internal.core.StartLevelManager.resumeBundles(StartLevelManager.java:634)
at org.eclipse.osgi.framework.internal.core.StartLevelManager.incFWSL(StartLevelManager.java:508)
at org.eclipse.osgi.framework.internal.core.StartLevelManager.doSetStartLevel(StartLevelManager.java:282)
at org.eclipse.osgi.framework.internal.core.StartLevelManager.dispatchEvent(StartLevelManager.java:468)
at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:195)
at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:297)
Caused by: java.lang.NullPointerException
at org.eclipse.osgi.internal.resolver.BundleDescriptionImpl.setExportPackages(BundleDescriptionImpl.java:208)
at org.eclipse.osgi.internal.resolver.StateReader.readBundleDescriptionLazyData(StateReader.java:255)
at org.eclipse.osgi.internal.resolver.StateReader.fullyLoad(StateReader.java:608)
at org.eclipse.osgi.internal.resolver.BundleDescriptionImpl.fullyLoad(BundleDescriptionImpl.java:456)
at org.eclipse.osgi.internal.resolver.BundleDescriptionImpl.getResolvedRequires(BundleDescriptionImpl.java:167)
at org.eclipse.osgi.framework.internal.core.BundleLoader.(BundleLoader.java:135)
at org.eclipse.osgi.framework.internal.core.BundleLoaderProxy.getBundleLoader(BundleLoaderProxy.java:56)
at org.eclipse.osgi.framework.internal.core.BundleHost.getBundleLoader(BundleHost.java:590)
at org.eclipse.osgi.framework.internal.core.BundleHost.checkLoader(BundleHost.java:196)
at org.eclipse.osgi.framework.internal.core.BundleHost.loadClass(BundleHost.java:223)
at org.eclipse.osgi.framework.internal.core.AbstractBundle.loadBundleActivator(AbstractBundle.java:134)
... 10 more
Root exception:
java.lang.NullPointerException
at org.eclipse.osgi.internal.resolver.BundleDescriptionImpl.setExportPackages(BundleDescriptionImpl.java:208)
at org.eclipse.osgi.internal.resolver.StateReader.readBundleDescriptionLazyData(StateReader.java:255)
at org.eclipse.osgi.internal.resolver.StateReader.fullyLoad(StateReader.java:608)
at org.eclipse.osgi.internal.resolver.BundleDescriptionImpl.fullyLoad(BundleDescriptionImpl.java:456)
at org.eclipse.osgi.internal.resolver.BundleDescriptionImpl.getResolvedRequires(BundleDescriptionImpl.java:167)
at org.eclipse.osgi.framework.internal.core.BundleLoader.(BundleLoader.java:135)
at org.eclipse.osgi.framework.internal.core.BundleLoaderProxy.getBundleLoader(BundleLoaderProxy.java:56)
at org.eclipse.osgi.framework.internal.core.BundleHost.getBundleLoader(BundleHost.java:590)
at org.eclipse.osgi.framework.internal.core.BundleHost.checkLoader(BundleHost.java:196)
at org.eclipse.osgi.framework.internal.core.BundleHost.loadClass(BundleHost.java:223)
at org.eclipse.osgi.framework.internal.core.AbstractBundle.loadBundleActivator(AbstractBundle.java:134)
at org.eclipse.osgi.framework.internal.core.BundleContextImpl.start(BundleContextImpl.java:970)
at org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java:346)
at org.eclipse.osgi.framework.internal.core.AbstractBundle.resume(AbstractBundle.java:350)
at org.eclipse.osgi.framework.internal.core.Framework.resumeBundle(Framework.java:1118)
at org.eclipse.osgi.framework.internal.core.StartLevelManager.resumeBundles(StartLevelManager.java:634)
at org.eclipse.osgi.framework.internal.core.StartLevelManager.incFWSL(StartLevelManager.java:508)
at org.eclipse.osgi.framework.internal.core.StartLevelManager.doSetStartLevel(StartLevelManager.java:282)
at org.eclipse.osgi.framework.internal.core.StartLevelManager.dispatchEvent(StartLevelManager.java:468)
at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:195)
at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:297)

!ENTRY com.adobe.flexbuilder.multisdk 4 0 2009-04-16 20:54:43.953
!MESSAGE
!STACK 0
org.osgi.framework.BundleException: The activator com.adobe.flexbuilder.multisdk.Activator for bundle com.adobe.flexbuilder.multisdk is invalid
at org.eclipse.osgi.framework.internal.core.AbstractBundle.loadBundleActivator(AbstractBundle.java:141)
at org.eclipse.osgi.framework.internal.core.BundleContextImpl.start(BundleContextImpl.java:970)
at org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java:346)
at org.eclipse.osgi.framework.internal.core.AbstractBundle.resume(AbstractBundle.java:350)
at org.eclipse.osgi.framework.internal.core.Framework.resumeBundle(Framework.java:1118)
at org.eclipse.osgi.framework.internal.core.StartLevelManager.resumeBundles(StartLevelManager.java:634)
at org.eclipse.osgi.framework.internal.core.StartLevelManager.incFWSL(StartLevelManager.java:508)
at org.eclipse.osgi.framework.internal.core.StartLevelManager.doSetStartLevel(StartLevelManager.java:282)
at org.eclipse.osgi.framework.internal.core.StartLevelManager.dispatchEvent(StartLevelManager.java:468)
at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:195)
at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:297)
Caused by: java.lang.NullPointerException
at org.eclipse.osgi.internal.resolver.BundleDescriptionImpl.setExportPackages(BundleDescriptionImpl.java:208)
at org.eclipse.osgi.internal.resolver.StateReader.readBundleDescriptionLazyData(StateReader.java:255)
at org.eclipse.osgi.internal.resolver.StateReader.fullyLoad(StateReader.java:608)
at org.eclipse.osgi.internal.resolver.BundleDescriptionImpl.fullyLoad(BundleDescriptionImpl.java:456)
at org.eclipse.osgi.internal.resolver.BundleDescriptionImpl.getResolvedRequires(BundleDescriptionImpl.java:167)
at org.eclipse.osgi.framework.internal.core.BundleLoader.(BundleLoader.java:135)
at org.eclipse.osgi.framework.internal.core.BundleLoaderProxy.getBundleLoader(BundleLoaderProxy.java:56)
at org.eclipse.osgi.framework.internal.core.BundleHost.getBundleLoader(BundleHost.java:590)
at org.eclipse.osgi.framework.internal.core.BundleHost.checkLoader(BundleHost.java:196)
at org.eclipse.osgi.framework.internal.core.BundleHost.loadClass(BundleHost.java:223)
at org.eclipse.osgi.framework.internal.core.AbstractBundle.loadBundleActivator(AbstractBundle.java:134)
... 10 more
Root exception:
java.lang.NullPointerException
at org.eclipse.osgi.internal.resolver.BundleDescriptionImpl.setExportPackages(BundleDescriptionImpl.java:208)
at org.eclipse.osgi.internal.resolver.StateReader.readBundleDescriptionLazyData(StateReader.java:255)
at org.eclipse.osgi.internal.resolver.StateReader.fullyLoad(StateReader.java:608)
at org.eclipse.osgi.internal.resolver.BundleDescriptionImpl.fullyLoad(BundleDescriptionImpl.java:456)
at org.eclipse.osgi.internal.resolver.BundleDescriptionImpl.getResolvedRequires(BundleDescriptionImpl.java:167)
at org.eclipse.osgi.framework.internal.core.BundleLoader.(BundleLoader.java:135)
at org.eclipse.osgi.framework.internal.core.BundleLoaderProxy.getBundleLoader(BundleLoaderProxy.java:56)
at org.eclipse.osgi.framework.internal.core.BundleHost.getBundleLoader(BundleHost.java:590)
at org.eclipse.osgi.framework.internal.core.BundleHost.checkLoader(BundleHost.java:196)
at org.eclipse.osgi.framework.internal.core.BundleHost.loadClass(BundleHost.java:223)
at org.eclipse.osgi.framework.internal.core.AbstractBundle.loadBundleActivator(AbstractBundle.java:134)
at org.eclipse.osgi.framework.internal.core.BundleContextImpl.start(BundleContextImpl.java:970)
at org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java:346)
at org.eclipse.osgi.framework.internal.core.AbstractBundle.resume(AbstractBundle.java:350)
at org.eclipse.osgi.framework.internal.core.Framework.resumeBundle(Framework.java:1118)
at org.eclipse.osgi.framework.internal.core.StartLevelManager.resumeBundles(StartLevelManager.java:634)
at org.eclipse.osgi.framework.internal.core.StartLevelManager.incFWSL(StartLevelManager.java:508)
at org.eclipse.osgi.framework.internal.core.StartLevelManager.doSetStartLevel(StartLevelManager.java:282)
at org.eclipse.osgi.framework.internal.core.StartLevelManager.dispatchEvent(StartLevelManager.java:468)
at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:195)
at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:297)

!ENTRY org.eclipse.osgi 4 0 2009-04-16 20:54:44.000
!MESSAGE Application error
!STACK 1
org.eclipse.core.runtime.CoreException: Plug-in org.eclipse.ui.ide.application was unable to load class org.eclipse.ui.internal.ide.application.IDEApplication.
at org.eclipse.core.internal.registry.osgi.RegistryStrategyOSGI.throwException(RegistryStrategyOSGI.java:180)
at org.eclipse.core.internal.registry.osgi.RegistryStrategyOSGI.createExecutableExtension(RegistryStrategyOSGI.java:162)
at org.eclipse.core.internal.registry.ExtensionRegistry.createExecutableExtension(ExtensionRegistry.java:788)
at org.eclipse.core.internal.registry.ConfigurationElement.createExecutableExtension(ConfigurationElement.java:243)
at org.eclipse.core.internal.registry.ConfigurationElementHandle.createExecutableExtension(ConfigurationElementHandle.java:51)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:165)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:106)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:76)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:363)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:176)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:508)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:447)
at org.eclipse.equinox.launcher.Main.run(Main.java:1173)
org.eclipse.core.runtime.CoreException[1]: java.lang.NullPointerException
at org.eclipse.osgi.internal.resolver.BundleDescriptionImpl.setExportPackages(BundleDescriptionImpl.java:208)
at org.eclipse.osgi.internal.resolver.StateReader.readBundleDescriptionLazyData(StateReader.java:255)
at org.eclipse.osgi.internal.resolver.StateReader.fullyLoad(StateReader.java:608)
at org.eclipse.osgi.internal.resolver.BundleDescriptionImpl.fullyLoad(BundleDescriptionImpl.java:456)
at org.eclipse.osgi.internal.resolver.BundleDescriptionImpl.getResolvedRequires(BundleDescriptionImpl.java:167)
at org.eclipse.osgi.framework.internal.core.BundleLoader.(BundleLoader.java:135)
at org.eclipse.osgi.framework.internal.core.BundleLoaderProxy.getBundleLoader(BundleLoaderProxy.java:56)
at org.eclipse.osgi.framework.internal.core.BundleHost.getBundleLoader(BundleHost.java:590)
at org.eclipse.osgi.framework.internal.core.BundleHost.checkLoader(BundleHost.java:196)
at org.eclipse.osgi.framework.internal.core.BundleHost.loadClass(BundleHost.java:223)
at org.eclipse.osgi.framework.internal.core.AbstractBundle.loadClass(AbstractBundle.java:1269)
at org.eclipse.core.internal.registry.osgi.RegistryStrategyOSGI.createExecutableExtension(RegistryStrategyOSGI.java:160)
at org.eclipse.core.internal.registry.ExtensionRegistry.createExecutableExtension(ExtensionRegistry.java:788)
at org.eclipse.core.internal.registry.ConfigurationElement.createExecutableExtension(ConfigurationElement.java:243)
at org.eclipse.core.internal.registry.ConfigurationElementHandle.createExecutableExtension(ConfigurationElementHandle.java:51)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:165)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:106)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:76)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:363)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:176)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:508)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:447)
at org.eclipse.equinox.launcher.Main.run(Main.java:1173)

!ENTRY org.eclipse.osgi 4 0 2009-04-16 20:54:44.093
!MESSAGE Shutdown error
!STACK 1
java.lang.NullPointerException
at org.eclipse.osgi.internal.resolver.BundleDescriptionImpl.setExportPackages(BundleDescriptionImpl.java:208)
at org.eclipse.osgi.internal.resolver.StateReader.readBundleDescriptionLazyData(StateReader.java:255)
at org.eclipse.osgi.internal.resolver.StateReader.fullyLoad(StateReader.java:608)
at org.eclipse.osgi.internal.resolver.BundleDescriptionImpl.fullyLoad(BundleDescriptionImpl.java:456)
at org.eclipse.osgi.internal.resolver.BundleDescriptionImpl.getExportPackages(BundleDescriptionImpl.java:117)
at org.eclipse.osgi.internal.resolver.StateHelperImpl.addReference(StateHelperImpl.java:260)
at org.eclipse.osgi.internal.resolver.StateHelperImpl.buildReferences(StateHelperImpl.java:250)
at org.eclipse.osgi.internal.resolver.StateHelperImpl.buildReferences(StateHelperImpl.java:244)
at org.eclipse.osgi.internal.resolver.StateHelperImpl.sortBundles(StateHelperImpl.java:227)
at org.eclipse.osgi.framework.internal.core.StartLevelManager.sortByDependencies(StartLevelManager.java:576)
at org.eclipse.osgi.framework.internal.core.StartLevelManager.sortByDependency(StartLevelManager.java:557)
at org.eclipse.osgi.framework.internal.core.StartLevelManager.getInstalledBundles(StartLevelManager.java:533)
at org.eclipse.osgi.framework.internal.core.StartLevelManager.doSetStartLevel(StartLevelManager.java:285)
at org.eclipse.osgi.framework.internal.core.StartLevelManager.shutdown(StartLevelManager.java:261)
at org.eclipse.osgi.framework.internal.core.SystemBundle.suspend(SystemBundle.java:188)
at org.eclipse.osgi.framework.internal.core.Framework.shutdown(Framework.java:622)
at org.eclipse.osgi.framework.internal.core.Framework.close(Framework.java:525)
at org.eclipse.osgi.framework.internal.core.OSGi.close(OSGi.java:41)
at org.eclipse.core.runtime.adaptor.EclipseStarter.shutdown(EclipseStarter.java:399)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:197)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:508)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:447)
at org.eclipse.equinox.launcher.Main.run(Main.java:1173)
!SESSION Thu Apr 16 20:54:44 CST 2009 ------------------------------------------
!ENTRY org.eclipse.equinox.launcher 4 0 2009-04-16 20:54:44.187
!MESSAGE Exception launching the Eclipse Platform:
!STACK
java.lang.NullPointerException
at org.eclipse.osgi.internal.resolver.BundleDescriptionImpl.setExportPackages(BundleDescriptionImpl.java:208)
at org.eclipse.osgi.internal.resolver.StateReader.readBundleDescriptionLazyData(StateReader.java:255)
at org.eclipse.osgi.internal.resolver.StateReader.fullyLoad(StateReader.java:608)
at org.eclipse.osgi.internal.resolver.BundleDescriptionImpl.fullyLoad(BundleDescriptionImpl.java:456)
at org.eclipse.osgi.internal.resolver.BundleDescriptionImpl.getExportPackages(BundleDescriptionImpl.java:117)
at org.eclipse.osgi.internal.resolver.StateHelperImpl.getExportedPackageMap(StateHelperImpl.java:74)
at org.eclipse.osgi.internal.resolver.StateHelperImpl.getUnsatisfiedLeaves(StateHelperImpl.java:109)
at org.eclipse.osgi.internal.resolver.StateHelperImpl.getUnsatisfiedLeaves(StateHelperImpl.java:145)
at org.eclipse.core.runtime.adaptor.EclipseStarter.logUnresolvedBundles(EclipseStarter.java:438)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:186)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:508)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:447)
at org.eclipse.equinox.launcher.Main.run(Main.java:1173)

[b]问题补充:[/b]
一加上-clean就能启动,但是感觉加上-clean是不是启动慢了呀,这样是治标不治本呀,有没有彻底的解决办法,这log记录能不能看出是那里出了问题,我好像感觉是RDT和flexbuilder的兼容性问题,不知道大家有没有什么好的解决办法?
[b]问题补充:[/b]
楼下的lovewhzlq哥们好像没明白我的问题呀,我的意思是说现在我的eclipse装了一些插件(应该说是N多),问题是现在启动的时候不加-clean启动不了,上面已经贴出了日志,就是说现在有什么办法不加这个-clean。加-clean感觉是治标不治本呀。
[b]问题补充:[/b]
要是Aptana的问题怎么解决呀哥们?
[b]问题补充:[/b]
哥们不知你说的启动不加载Aptana插件是什么意思呀?是不安装吗,还要是把他标用掉?如果不是的话应该如何设置呀.烦指教.
[b]问题补充:[/b]
试了还是不行呀,好你是装了RUBY的开发插件的问题.我看还是加-clean吧

如上面,把里面的Aptana打钩去掉就OK了

一般加-clean之后,第二次启动就没有什么问题,。。这问题的确很烦,在linux更严重,随着插件的增多,一些莫名的原因,eclipse稳定性会越来越差,安装之后最好查阅相关资料,保证兼容性。
如果还有问题,就删除workspace下的.metadata目录,再重新启动eclipse。

安装插件后在窗口— > 首选项 中看不到

① 把 eclipse\configuration\org.eclipse.update 删除掉。出现这种情况的原因是在你安装新的插件以前你启动过 eclipse ,在 org.eclipse.update 文件夹下记录了插件的历史更新情况,它只记忆了以前的插件更新情况,而你新安装的插件它并不记录,所以删除掉这个文件夹就可以解决这个问题了,不过删除掉这个文件夹后, eclipse 会重新扫描所有的插件,此时再重新启动 eclipse 时可能会比刚才稍微慢点。

② 创建一个 Eclipse 快捷启动方式,在目标栏中加入一个“ 空格— clean ”参数,注意不要把— clean 前面的空格漏掉。或者在菜单【开始】—【运行】中启动你的 eclipse 时加上— clean 参数,如我的可以在“运行”中输入: F:\hongjun\eclipse\eclipse.exe –clean

如果启动 eclipse 后找到你所安装的新插件后,在下次启动之前把参数 clean 去掉就可以了。

③ 如果 Eclipse 启动找不到插件的话,解决办法是在 eclipse\configuration 目录下的 config.ini 文件中加入一行 : osgi.checkConfiguration=true

这样它就会寻找并安装插件 , 找到插件后可以把该行注释掉 ( 去掉 ), 这样以后每次启动就不会因为寻找插件而显得慢了。

你只要安装了新插件就得-clean去启动,才能更新到这些插件啊,

这样安装插件也行

一、使用links方式安装eclipse插件
  
  假设eclipse安装目录是D:\eclipse,待安装插件目录是D:\eclipseplugins。以lomboz,Sysdeo Eclipse Tomcat Launcher plugin和xmlbuddy为例说明如何使用links方式安装eclipse插件。
  
  1、安装Lomboz
  
  在D:\eclipseplugins中建立如下的目录结构:
  
  D:\eclipseplugins\lomboz\eclipse
  
  将lomboz安装文件解压到此目录中,这个目录将包含一个plugins目录,即目录结构是这样的:
  
  D:\eclipseplugins\lomboz\eclipse\plugins
  
  在D:\eclipse\links目录下新建文件,命名为lomboz.link,编辑此文件,加入如下内容并保存。
  
  path = D:/eclipseplugins/lomboz
  
  eclipse将会到指定的目录下去查找eclipse\features目录和eclipse\plugins目录,看是否有合法的功能部件和(或)插件。也就是说,目标目录必须包含一个 \eclipse 目录。如果找到,附加的功能部件和插件在运行期配置是将是可用的,如果链接文件是在工作区创建之后添加的,附加的功能部件和插件会作为新的配置变更来处理。
  
  其它压缩文件解压后若已经包含eclipse\plugins目录,则不需要建立eclipse目录。
  
  2、安装Sysdeo Eclipse Tomcat Launcher plugin
  
  解压tomcatPluginV3.zip到目录D:\eclipseplugins\tomcatPlugin\eclipse\plugins目录下。
  
  在D:\eclipse\links下新建文件,命名为tomcatPlugin.link,编辑此文件,加入如下内容并保存。
  
  path = D:/eclipseplugins/tomcatPlugin
  
  3、安装xmlbuddy
  
  解压xmlbuddy安装文件到D:\eclipseplugins\xmlbuddy\eclipse\plugins目录下。
  
  在D:\eclipse\links下新建文件,命名为xmlbuddy.link,编辑此文件,加入如下内容并保存。
  
  path = D:/eclipseplugins/xmlbuddy
  
  二、插件管理
  
  启动eclipse,在菜单Help->Software Updates->Manage Configuration...下,启用或者禁用插件。
  
  三、说明
  
  1. 插件可以分别安装在多个自定义的目录中。
  
  2. 一个自定义目录可以安装多个插件。
  
  3. link文件的文件名及扩展名可以取任意名称,比如ddd.txt,myplugin都可以。
  
  4. link文件中path=插件目录的path路径分隔要用\或是/
  
  5. link文件可以有多行path=插件目录,对应多个自定义插件目录,每一行的path参数都将生效。
  
  6. 在links目录也可以有多个link文件,每个link文件中的path参数都将生效。
  
  7. 插件目录可以使用相对路径。
  
  8. 可以在links目录中建立一个子目录,转移暂时不用的插件到此子目录中,加快eclipse启动。
  
  9. 如果安装后看不到插件,把eclipse安装目录下的configuration/org.eclipse.update/目录整个删除,重启eclipse。

你这哪里拷过来的,在最新的eclipse,根本就不是这么回事。

Windows 下 eclipse 还是要稳定很多,linux下的 eclipse 问题不断,根本就没有办法使用。
我以前在博客描述这方面的问题。

有问题加了-clean也不会解决问题,删除~/workspace/.metadata目录和 eclipse下的configuration,重新拷贝一份新的configration。
有问题可以报到eclipse bug tracker上去,老外还是比较热情的。

偶也是遇到这个问题,事更新Aptana

Aptana捣鬼,看看Aptana支持的版本吧 哈哈

在Eclipse中把Aptana启动加载去掉就OK了,也就是启动不加载Aptana插件

Eclipse-Window-Preference-General-Start up and Shutdown

apanta要使用的话,专门下载一个官方集成版本,那东西的确问题多多。

哦,Ruby就不了解了,呵呵,工具嘛,能用就行!