| Different deployment products for RCP application with maven [message #1690490] |
Fri, 27 March 2015 11:27  |
Eclipse User |
|
|
|
Hi,
I have got an RCP application which is defined by the following projects:
- Application Project (including e4xmi)
- Feature Definition
- Target Platform
- Product
Now, I would like to add some optional functionality by defining a plug-in with a fragment.e4xmi.
My idea was to just create an additional product projekt which has a dependency for the new plug-in.
Is this the right approach to do this?
Thanks for any advice!
|
|
|
| Re: Different deployment products for RCP application with maven [message #1693563 is a reply to message #1690490] |
Sat, 25 April 2015 07:14  |
| Eclipse User |
|
|
|
I did something similar, using Tycho, that is a maven plugin, and it is working as follows:
consider having two projects, one called MyPlatform and the other called MyPlugin.
- MyPlatform contains the Application.e4xmi
- MyPlugin contains the Fragment.e4xmi which is based on the platform application.e4xmi
for each of the two projects above you will need 5 eclipse projects:
- project.bundle : contains the real plugin classes, the application xmi, etc.
- project.test : contains the test classes
- project.parent : it is used to start the maven build
- project.feature : it groups the plugins needed for the project in one feature
- project.repository : it is the place where maven/tycho is going to generate your build artifacts.
I initially used the Target platform, but I get rid of it at a later stage of the project since it is not needed anymore.
Now I'm just using plugins/features defined in the product file.
If you're interested in using Tycho, see these useful references:
|
|
|
Powered by
FUDForum. Page generated in 0.04171 seconds
Home