通过软件更新安装时,为Eclipse 3.4+插件指定目标文件夹

时间:2021-07-11 00:03:43

After searching around I see that eclipse 3.4/3.5 now allow you to use their 'dropin' folder to manually install plugins.

搜索后我发现eclipse 3.4 / 3.5现在允许你使用他们的'dropin'文件夹来手动安装插件。

This works well in a situation where you have already downloaded the feature and plugin files, however in cases where you use the Software Updates feature to simply point to a URL and download a plugin, you don't appear to have control over what folder the plugin is installed into.

这在您已经下载了功能和插件文件的情况下运行良好,但是如果您使用软件更新功能简单地指向URL并下载插件,则您似乎无法控制哪个文件夹插件已安装到。

Is it possible to force plugins to be installed to an arbitrary dropin folder, or otherwise export a plugin to a location so that it can be shared with other people's eclipse installations?

是否可以强制插件安装到任意dropin文件夹,或以其他方式将插件导出到某个位置,以便可以与其他人的eclipse安装共享?

I'd prefer not to have to comb through the plugin info and manually determine which plugin jars to copy into a dropin folder :P

我宁愿不必梳理插件信息并手动确定将哪些插件jar复制到dropin文件夹中:P

Thanks

4 个解决方案

#1


I think the answer in this thread and the mentioned blog post of Michael Scharf can be useful for you, although the procedure is not as simple as it should be :(

我认为这个帖子和Michael Scharf提到的博客文章中的答案可能对你有用,虽然程序并不像应该的那样简单:(

#2


The new p2 system in 3.4 is supposed to have a feature called bundle pooling that allows for shared plugins. However, I haven't used it, so I'm not sure about the particulars. I hope this at least points you in the right direction.

3.4中的新p2系统应该具有一个称为捆绑池的功能,允许共享插件。但是,我没有使用它,所以我不确定细节。我希望这至少能指出你正确的方向。

#3


When using 3.4.1 you can still enable the "old" update manager in Preferences/ General/ Capabilities. Then you can use the extension points again. But it has been removed in 3.4.2 completely.

使用3.4.1时,您仍然可以在Preferences / General / Capabilities中启用“旧”更新管理器。然后,您可以再次使用扩展点。但它已在3.4.2中完全删除。

#4


You have to remove P2 to get the old update manager.

您必须删除P2才能获得旧的更新管理器。

Note: The P2 team managed to broke everything backward compatible. This tricks does not work with 3.5.

注意:P2团队成功地将所有内容向后兼容。这个技巧不适用于3.5。

#1


I think the answer in this thread and the mentioned blog post of Michael Scharf can be useful for you, although the procedure is not as simple as it should be :(

我认为这个帖子和Michael Scharf提到的博客文章中的答案可能对你有用,虽然程序并不像应该的那样简单:(

#2


The new p2 system in 3.4 is supposed to have a feature called bundle pooling that allows for shared plugins. However, I haven't used it, so I'm not sure about the particulars. I hope this at least points you in the right direction.

3.4中的新p2系统应该具有一个称为捆绑池的功能,允许共享插件。但是,我没有使用它,所以我不确定细节。我希望这至少能指出你正确的方向。

#3


When using 3.4.1 you can still enable the "old" update manager in Preferences/ General/ Capabilities. Then you can use the extension points again. But it has been removed in 3.4.2 completely.

使用3.4.1时,您仍然可以在Preferences / General / Capabilities中启用“旧”更新管理器。然后,您可以再次使用扩展点。但它已在3.4.2中完全删除。

#4


You have to remove P2 to get the old update manager.

您必须删除P2才能获得旧的更新管理器。

Note: The P2 team managed to broke everything backward compatible. This tricks does not work with 3.5.

注意:P2团队成功地将所有内容向后兼容。这个技巧不适用于3.5。