插件产品VS特色产品 [英] Plugin product VS Feature product

问题描述

在RCP应用程序的上下文中，我想知道我是否应该将产品放在插件或功能上。

现在我可以看到的主要区别是导出的应用程序的内容。

使用插件作为产品库导出（使用GUI或无头构建，它是一样的）所有所需的插件（计算我猜猜通过插件清单）。

相反，当使用功能作为基础时，导出的产品只包含产品文件中列出的功能。因此，我必须手动添加所有必需的功能，以使我的产品正常工作。即使不需要，这也带来了所有功能插件的副作用。

您有什么经验？

编辑如Vonc所示评论我创建了自己的功能，包括我需要的其他功能插件。这个解决方案是有效的，但是我必须在这个功能中手动添加我的产品所需的所有插件。今天要做的是，我发现唯一的解决方案是使用启动配置插件tabb与计算所需的插件按钮，并手动报告我的功能所有选定的插件。真的很无聊:-(有没有其他的解决方案存在？

谢谢

解决方案>

经过多次调查，这是一个关于这个问题的清晰（我希望）的状态。

插件产品：

• 建立（Gui或headless）=>所有必需（与调试应用程序时启动配置对话框中计算的所需插件相同）没有问题）插件存在


• RCP应用程序磁盘空间被优化!!没有无用的插件


• 没有功能被导出：作为ressult功能列表选项卡关于对话框是空的!!!


• 似乎插件产品不推荐用于自动更新的RCP（我没有测试过）

功能产品

• 导出时（无头），唯一的现有插件和功能是.product文件
中列出的插件和功能

• 需要创建一个依赖功能，包括所有必需的插件 OR ，取决于包含所需插件的所有功能=>带来大量无用插件


• 在对话框中列出的功能

在我的个人情况下，我决定使用功能产品，然后手动创建一个功能，包括我的RCP所需的所有90个插件。因为我很懒又恨重复任务，所以我写了一个简单的Java主要解析一个启动配置文件（.launch位于工作区元数据文件夹中），并从一个模板生成该功能具有所有必需的依赖关系。

希望这可以帮助别人，如果您需要我简单的Java功能依赖性创建者，请问它。

Manu

In the context of an RCP application I am wondering if I should base my product on plugins or on features.

The main difference I can see for now is about the content of the exported application.

Using plugins as product base result in an exported (with GUi or headless build, it's the same) with ALL the required plugins (computed I guess through plugins manifest).

On the opposite, when using feature as bases the exported product only contain the listed features in the product file. Thus I have to add manually add all the required features in order to let my product work correctly. This also has the side effect to bring all the features plugins even if they are not needed.

What are your experiences on the subject ?

EDIT As suggested by Vonc comments I created my own feature including only plugins I need from other features. This solution works but I have to manually add all the required plugins by my product in this feature. Today to do that, the only solution I found is to use the launch configuration plugins tabb with the compute required plugins button and to report by hand in my feature all the selected plugins. It's really boring :-( Is there any other solutions existing ?

Thanks

解决方案

After many investigations here is a "clear" (I hope) status on the subject.

Plugin Products:

• No problem when building (Gui or headless) => all the required (the same than the required plugins computed in the launch configuration dialog when debugging the app) plugins are present
• The RCP application disk footprint is optimized !! No useless plugins
• No features are exported: as a ressult the features list tab of about dialog is empty !!!
• It seems that plugin products are not recommended for RCP with self update (I didnd't tested that yet)

Feature Products:

• When exporting (headless), the only present plugins and features are the one listed in the .product file
• Need to create a "dependencies" features including all the required plugins OR depend on all the features containing the required plugins => bring a lot of useless plugins
• Features listed in the about dialog

In my personal situation, I decided to use a Feature Product and then to "manually" create a feature including all the 90 plugins required by my RCP.

Because I am lazy and hate repetitive tasks, I wrote a simple Java main parsing a launch configuration file (.launch located in the workspace metadata folder) and generating from a template the feature with all the required dependencies.

Hope this can help others, and if you need my simple Java feature dependency creator, just ask it.

Manu

这篇关于插件产品VS特色产品的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！