新版本的 Eclipse 刚刚发布。 我可以做些什么来避免再次手动寻找我的插件吗?

发布于 2024-07-25 07:27:15 字数 252 浏览 8 评论 0原文

Galileo 前几天发布了,尽管 Eclipse 下的插件在我看来比 Netbeans,如果有一种简单的方法可以让我升级,那就太棒了到新版本(并随身携带我的插件)。

有小费吗?

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).

Any tips?

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(6

刘备忘录 2024-08-01 07:27:15

不直接,据我所知。

这是我想到的最接近的东西,假设我的旧 Eclipse 足够新,因此它使用类似形式的更新管理器 (P2)。

在旧版 Eclipse 中,转到首选项 -> 安装/更新 -> 可用软件站点。
选择那些不是内置的(您将看到它们的名称,或者至少是一个非 Eclipse URL)。 您可以选择所需的内容,然后将其导出为 XML。

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

重要警告:一些插件供应商实际上为不同的 Eclipse 版本提供不同的更新站点,因此您仍然会指向旧插件。 如果您从未将现有插件更新到新版本,通常会发生这种情况。 一个常见的示例是 Subslipse,因此您可能需要手动升级该版本。

Not directly, 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).

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.

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.

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.

℡寂寞咖啡 2024-08-01 07:27:15

查看此博客条目:如何让您的 Eclipse 插件列表在 Eclipse 升级后仍然存在

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

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

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.

贱贱哒 2024-08-01 07:27:15

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

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

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

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

将其与 微调的 eclipse.ini 结合起来,就可以了走吧!

I would recommend to read: "Install Plug-ins into Eclipse IDE", specifically written for 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:

-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.

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

梦里寻她 2024-08-01 07:27:15

我这样做:

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

不确定我有多喜欢这种方法 - 我仍在尝试。 本质上,我可以为每个插件安装创建一个补丁,并将其应用到新版本。

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

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.

○愚か者の日 2024-08-01 07:27:15
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"

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"

~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文