Eclipse的新版本刚刚问世。有什么我可以做的，以避免不得不再次手动搜索我的插件？

Galileo came out the other day, and even though plugins under Eclipse are, IMO, just a little bit easier to deal with than Netbeans, it would still be really awesome if there was a simple way for me to upgrade to the new version (and take my plugins with me).

Galileo前几天问世，即使Eclipse下的插件是IMO，比Netbeans更容易处理，如果有一种简单的方法可以升级到新版本，它仍然会非常棒（和带上我的插件）。

Any tips?

有小费吗？

6 个解决方案

#1

Not directly, AFAIK.

不直接，AFAIK。

Here is the closest thing I came up with, under the assumption that my old Eclipse is recent enough so that it uses a similar form of update manager (P2).

这是我提出的最接近的事情，假设我的旧Eclipse已经足够，以便它使用类似形式的更新管理器（P2）。

In the old Eclipse, go to preferences->Install/Update->Available Software Sites. Pick the ones that are not built in (you will see a name for them, or at least a non-eclipse URL). You can select the ones you want and then export them to XML.

在旧的Eclipse中，转到首选项 - >安装/更新 - >可用软件站点。选择那些没有内置的（您将看到它们的名称，或至少是非日食URL）。您可以选择所需的那些，然后将它们导出到XML。

Now go to the new Eclipse, go to the same preference window, and import the update sites from the XML. Now, when you install new software, you should see your update sites although you will probably still have to manually pick options for plugins that offer multiple downloads.

现在转到新的Eclipse，转到相同的首选项窗口，然后从XML导入更新站点。现在，当您安装新软件时，您应该会看到更新站点，尽管您可能仍需要手动选择提供多个下载的插件选项。

Important caveat: Some plugin vendors actually offer different update sites for different Eclipse versions, so you would still be pointing at the old plugin. This would typically happen if you never updated your existing plugin to a new version. One common example of this is with Subsclipse, so you may want to manually upgrade that one.

重要提示：一些插件供应商实际上为不同的Eclipse版本提供了不同的更新站点，因此您仍然会指向旧的插件。如果您从未将现有插件更新为新版本，通常会发生这种情况。一个常见的例子是Subsclipse，所以你可能想手动升级那个。

#2

Take a look into this blog entry: How to make your Eclipse plugin list survive an Eclipse upgrade

看看这篇博客文章：如何使Eclipse插件列表在Eclipse升级后继续存在

I also used the Yoxos service to build my "own" Eclipse distribution. I guess it should be easy possible to just upgrade the core elements in such a profile, keeping the plugins. It has included dependency checking, so it's very nice to get a distribution running.

我还使用Yoxos服务来构建我自己的Eclipse发行版。我想在这样的配置文件中升级核心元素应该很容易，保留插件。它包含了依赖性检查，因此让分发运行非常好。

#3

I would recommend to read: "Install Plug-ins into Eclipse IDE", specifically written for eclipse3.5.

我建议阅读：“将插件安装到Eclipse IDE中”，专门为eclipse3.5编写。

The method I use is to store all my plugin into one share a Dropins folder, and then launch my eclipse with the following line in the eclipse.ini:

我使用的方法是将我的所有插件存储到Dropins文件夹的一个共享中，然后在eclipse.ini中使用以下行启动我的eclipse：

-Dorg.eclipse.equinox.p2.reconciler.dropins.directory=/<myPath>/mySharedDropins

As long as this line is present in the eclipse.ini of any future eclipse, all of those new installation will detect and use my shared plugin.

只要这行存在于任何未来eclipse的eclipse.ini中，所有这些新安装都将检测并使用我的共享插件。

Combine that with a fine-tuned eclipse.ini and you are good to go!

将它与经过微调的eclipse.ini相结合，您就可以开始了！

#4

Try http://www.poweredbypulse.com/

试试http://www.poweredbypulse.com/

#5

I do this:

我这样做：

http://coders-log.blogspot.com/2009/06/manage-your-eclipse-install-with-local.html

Not sure how well I like the approach yet - I'm still trying it out. Essentially, I can create a patch of each plugin install, and the apply it to the new version.

不知道我对这种方法有多喜欢 - 我还在尝试。基本上，我可以创建每个插件安装的补丁，并将其应用到新版本。

Plus, I use this approach on other products, so I can use the same process everywhere.

另外，我在其他产品上使用这种方法，因此我可以在任何地方使用相同的流程。

#6

In many cases you may/should be able to copy the plugin files from your Eclipse 3.4 
install directory (i.e. eclipse/plugins) over to your new Galileo plugins directory.

There are some exceptions, but they tried to keep the plugin API and binaries 
backwards compatible with the previous release.  

You can find more information in the eclipse/readme directory under your 
Galileo install directory.  

See filename: readme_eclipse.html      Section: "Compatibility with Previous Releases"

#1