I agree with this approach.
Another possibility would be to create our own p2 server somewhere
and use that for the Ptolemy II dependencies.
Once the Ptolemy II code passes the IP process, then we can create
Ptolemy II bundles and they will be available on the Eclipse
servers.
http://www.vogella.com/tutorials/EclipseTycho/article.html#tychotargetplatform
says:
Tycho only supports Software Sites as locations. Directory,
Installation and Feature are not supported and are ignored by
the build process.
I think this means that in the near term, the Tycho build won't be
able to build Triquetrum target that can run because Tycho can't
deal with the bundles that are in directories.
_Christopher
On 1/25/16 1:03 AM, Erwin de Ley wrote:
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
_______________________________________________
triquetrum-dev mailing list
triquetrum-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or
unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/triquetrum-dev
--
Christopher Brooks, PMP University of California
Academic Program Manager & Software Engineer US Mail: 337 Cory Hall
CHESS/iCyPhy/Ptolemy/TerraSwarm Berkeley, CA 94720-1774
cxh@xxxxxxxxxxxxxxxxx, 707.332.0670 (Office: 545Q Cory)
|
