[triquetrum-dev] Using a dependencies wrapper bundle vs a target platfor

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

The maven/tycho build for Triquetrum currently uses a 
org.eclipse.triquetrum.dependencies bundle that contains all Ptolemy II 
bundles and exports their contents. This was the fast-track solution to 
include them in the build, as there is no p2 repository yet for those 
dependencies.

However using this approach implies that the ptolemy bundles in there 
are "treated as plain jars", and are not launched as bundles themselves 
when running the Triquetrum RCP. And that causes issues as the bundles 
have activators and DS components that don't do their thing in this 
setup, which results in problems with actor class loading etc.

So I have adapted the 
org.eclipse.triquetrum.workflow.editor/Triquetrum.product again to 
contain the individual ptolemy bundles, i.o. the dependencies wrapper 
bundle. This implies that the target definition was also adapted again, 
containing the ptolemy bundles again, and in your eclipse workspace for 
Triquetrum, you need to set the target again from 
org.eclipse.triquetrum.target.platform/triq.target.

This is available from the master branch.

To summarize :
- for the maven/tycho command-line build, we're using 
org.eclipse.triquetrum.dependencies as a container for the ptolemy 
dependencies, combined with p2 repositories of eclipse to get all other 
dependencies.
- for your eclipse workspace, and running the Triquetrum editor from 
there, you need to use the org.eclipse.triquetrum.target.platform and 
not the dependencies wrapper bundle.

regards
erwin