Hi,
Oomph doesn’t use the *.target files to provision the PDE Target; it builds its modular target independently of any of that.
We had briefly discussed, early on, the notion of teaching Oomph to generate the targets from the TPDs so that we could unify our workspace and build target definitions. But, this doesn’t work, because the Modular Target mechanism in Oomph is bigger than Papyrus-RT: any other projects that a developer imports from other setups also will contribute to the modular target, and PDE can only have one active target, so you can’t mix Oomph’s modular target with *.target files.
The only way I could see would be to develop an Oomph extension that synthesizes a dynamic Targlet from a *.TPD during the setup execution. This would be cool. On 14 July, 2016 at 12:47:16, Ernesto Posse (eposse@xxxxxxxxxxxxx) wrote:
I only tried re-creating the .target(s) but that
didn't work. Re-setting the targets the the 'papyrusrelease' TP
seems to work for the *.compare.* plugins, but it breaks the
*.migration.* plugins. Resetting to the 'papyrusnightly' TP seems
to work.
Still, I wonder if we could make Oomph create the .target(s)
and set the default TP.
Hi Ernesto,
The resolution of the dependencies worked for me so that there
are now compile errors on the compare projects. Did you re-set the
target manually to test if it isn't just a caching issue?
Thanks and best wishes,
Philip
_______________________________________________
papyrus-rt-dev mailing list
papyrus-rt-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or
unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/papyrus-rt-dev
_______________________________________________
papyrus-rt-dev mailing list
papyrus-rt-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/papyrus-rt-dev
|