RCP based on plugins or features ??

views:

answers:

+1 Q:

RCP based on plugins or features ??

Hi all,

I have an RCP application based on plugins because I started this app from a simple Mail example.

I am now wondering what is the difference between an RCP application based on features compare to one based on plugins ?

For information, my RCP will maybe require some advanced features such as headless build, or self update. May be this can impact on the choice of using plugins or features as basis ?

Thanks in advance

Manuel

+2 A:

Since features are just a collection of plugins (aka, a "packaging" process), you should be able to do in a PDE headless build what you can do with the PDE GUI.

The PDE build page does mention:

Building plug-ins, fragments or features consists of the 3 stages: fetch, generate scripts and build that are described bellow.

You could have some issue for modified plugin, but building features or a final product should work.

VonC 2010-06-29 10:51:37

Thanks again for your help. In fact I am stilling having problem and questions.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. To work, I have to add manually all the required features. This also has the side effect to bring all the features plugins even if they are not needed. Should I open an other question for that ?

Manuel Selva 2010-06-29 11:34:27

@Manuel: probably. the context of that new question would be clearer.

VonC 2010-06-29 11:36:55

here it is http://stackoverflow.com/questions/3140299/plugin-product-vs-feature-product

Manuel Selva 2010-06-29 11:45:13

ansaurus

tags:

views:

answers:

RCP based on plugins or features ??

related questions