[triquetrum-dev] Setting up an RCP build for Triquetrum

[Erwin de Ley <erwin.de.ley@xxxxxxxxxx>]

To finalize the #48 issue, we need a reproducible and p2-enabled RCP 
build for Triquetrum.

And then it's possible to use the standard eclipse workbench "Install 
new software" to upload new actors and other Triquetrum extensions, 
either from a p2 site or a plain feature zip.

To get that rolling, I've been doing the following :
- implement an example of an extra actor + feature definition + p2.inf 
instructions to let it auto-start when installed in the RCP
- define feature projects for the different parts of Triquetrum and for 
its non-std-eclipse dependencies
- define a feature-based product file
- add a repository project with a pom to define the build for the 
triquetrum p2 repository and a packaged RCP
- adapted the parent pom to add a bunch of new modules etc
- probably some more stuff that I've already forgotten about
- and finally created a personal p2 site for ptolemy's bundles at 
http://users.telenet.be/triquetrum-ptolemy-p2/
- adapted the pom and target to point only to p2 repositories
(So now we can remove the ptolemy dependencies from the github 
repository if we want.)
- tested the resulting build and : it WORKS! And there's even a working 
RCP there, somewhere deep in the maven build folders.


Question is now : "to commit and merge" or "not to commit and merge" ? ;-)

Christopher, can you evaluate what this would mean for the HIPP build?

Do I just push and merge into master and then fingers-crossed?

cheers
erwin