Plugin product VS Feature product?

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

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.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.