Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Rich Client Platform (RCP) » Feature-based product: What can I use insteaod of "Add Required Plug-ins" button
Feature-based product: What can I use insteaod of "Add Required Plug-ins" button [message #504378] Fri, 18 December 2009 15:10 Go to next message
Mickael Istria is currently offline Mickael Istria
Messages: 765
Registered: July 2009
Location: Grenoble, France
Senior Member
Hi all,

We are moving our RCP build from a simple and well=working plugin-based product definition to a (more complex) feature-based definition, to leverage p2.

I used to define my product by adding in the plugins list all org.bonitaoft.* bundles, and then by clicking on "Add Required Plugin", and then by adding platform-specific bundle to run on Mac, Linux and Win. Everything was perfect.
Now that I use feature-based, I'd like to have 2 features: one containing all org.bonitasoft code and one containing dependencies (the minimal set of plugins to get the product working). But this is very very very (to be repeated on 3 lines) difficult to maintain compared to the magic "Add Required plugins" button. The ideal would be a button on the feature that contains our bundle, that would be "Create a feature from required plugins"., but such a thing does not exist (yet ;).

Then I wonder whether I am missing a good practice about dependency management when using features? Can someone teach me something that will make me forget my love-story "Add required plugins" button?

Thanks in advance
--
Mickael Istria - BonitaSoft S.A.
http://www.bonitasoft.com/products/downloads.php
Re: Feature-based product: What can I use insteaod of "Add Required Plug-ins" button [message #505929 is a reply to message #504378] Tue, 05 January 2010 10:22 Go to previous message
Paul Webster is currently offline Paul Webster
Messages: 6859
Registered: July 2009
Location: Ottawa
Senior Member

Eclipse provides 2 features that can be consumed: org.eclipse.rcp and
org.eclipse.platform. They're not very granular, but org.eclipse.rcp
might get most of your dependencies.

your best option is to create your own "eclipse target feature" and have
your feature depend on it.

The target feature only has to change when you decide to pick up a new
plugin from the eclipse target platform (which shouldn't be done
lightly, unless your product is in early stages and is expanding its
feature set regularly). But you're right, it's not easy to populate the
initial list of bundles that are used.

PW

--
Paul Webster
http://wiki.eclipse.org/Platform_Command_Framework
http://wiki.eclipse.org/Command_Core_Expressions
http://wiki.eclipse.org/Menu_Contributions
http://wiki.eclipse.org/Menus_Extension_Mapping
http://help.eclipse.org/galileo/index.jsp?topic=/org.eclipse .platform.doc.isv/guide/workbench.htm


Previous Topic:Feature Tab in installation Details
Next Topic:RCP app has horrible remote performance
Goto Forum:
  


Current Time: Wed Oct 22 12:34:20 GMT 2014

Powered by FUDForum. Page generated in 0.03146 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software