|Re: [mdt-papyrus.dev] Collaborative-Modeling Target Platform|
In short :
- The target platform only import the sysml14.profile plugin 
- You add a dependency to sysml14.architecture which is unknown to the target platform 
ð Exception! Add the SysML 1.4 Feature to the target platform and it will fix your problem.
More on that (IMHO):
- Alll components should use tpd only on latest released version
- Developer tooling should be moved in SDK feature (Removing dependency to hudson update site)
- Collaborative shouldn’t depend from SysML 1.4 (From what I see, it’s for testing purposes. If possible use the UML standard profile that is provided by Papyrus core and UML Project)
1 : https://git.eclipse.org/c/papyrus/org.eclipse.papyrus-collaborativemodeling.git/tree/releng/targetplatforms/org.eclipse.papyrus.collaborativemodeling.targetplatform/org.eclipse.papyrus.collaborativemodeling.targetplatform.tpd
From what I can see the target used for the builds is the main one (under releng/targetplatforms) that includes the released  version of sysml14 on a lazy basis hence the latest oxygen’s 1.0.0. There is a parameter for the nightly of compare main and tests, that do require sysml14, but even they point to the released version of sysml14 from what I can see.
If all that is needed is to point to the nightly of sysml14 that could be possible by modifying the **.tpd. A little warning though, those are just here to ease the creation/visualization of the target files so those would have to be recalculated as well using Mikael’s tool .
As for the question about the particular platform needed to be followed by compare, I will let Camille or Philip answer. J
I could not reproduce the problem locally but I will try to build the repo on a linux VM and clean m2t o see if it changes anything.
What is the target platform of the Collaboration Modeling builds (specifically, Papyrus Compare) supposed to be? I have a Gerrit patch that is failing  because it is doesn’t find the Architecture Definition bundles from SysML14 version 1.1. Is the TP not supposed to be at least Oxygen for nightly builds in the Photon development stream?
Perhaps it’s just a matter of updating the target definition to take another SysML build, which is only a test dependency, anyways. Would it be okay if I did that? I ask the more general question because this problem reminds me that I don't know how the TP is intended to be maintained, what platform versions this (sub-)project wants to support, and how that may all be different to what EMF Compare is doing (and formerly did with these plug-ins).
Back to the top