Hi,
The Papyrus-RT RSA model migration extension cannot be built against Papyrus Neon release because it requires new behaviour in Papyrus Neon.1 (the maintenance stream).
So, only the “nightly” or, whenever a milestone build of Neon.1 is available, the “milestones” target-platform definition will do. The release TP will not work for this component.
In the general case, because Papyrus-RT 0.8 will be targeting Neon.1, we have no use for the Neon release target at all, I suppose.
On 28 June, 2016 at 04:20:30, Céline JANSSENS (celine.janssens@xxxxxxxxxxx) wrote:
Hello Ernesto,
I have disable the Gerrit job for Codegen. Thus, you can try
again.
To answer your question:
1) I don't know why we get this migration.rsa error. I still have
to investigate on this;
2) The Bug 469722 should make the codegen pom.xml a child of the
papyrus-rt/pom.xm which is not yet the case. As soon as it will be
the child of papyrus-rt/pom.xm, the profile that depends on the
codegen can be launched.
For the moment it is not working, because the papyrus-rt/pom.xml,
doesn't know the umlrt.code-generator pom.xml.
3) You're right, as said in point 2) ;)
Best regards
Le 27/06/2016 à 17:23, Ernesto Posse a
écrit :
[ERROR] Cannot resolve dependencies of MavenProject: org.eclipse.papyrusrt:org.eclipse.papyrusrt.umlrt.migration.rsa:0.7.2-SNAPSHOT @ /jobs/genie.papyrus-rt/Papyrus-RT-Gerrit-Codegen/workspace/source/plugins/umlrt/migration/org.eclipse.papyrusrt.umlrt.migration.rsa/pom.xml: See log for details -> [Help 1]
org.apache.maven.MavenExecutionException: Cannot resolve dependencies of MavenProject: org.eclipse.papyrusrt:org.eclipse.papyrusrt.umlrt.migration.rsa:0.7.2-SNAPSHOT @ /jobs/genie.papyrus-rt/Papyrus-RT-Gerrit-Codegen/workspace/source/plugins/umlrt/migration/org.eclipse.papyrusrt.umlrt.migration.rsa/pom.xml
This is a big problem because it now blocks us from merging
anything in codegen.
So, a few questions:
1) Why do we get that error?
2) The new codegen job has a message saying "(Wait for Bug
469722 before activate this on)" but that bug has not been closed
yet, so why activate this job now? Shouldn't this job be disabled
until the bug is closed?
3) The new job seems to start from source/pom.xml. I assume
that's the parent pom, rather than the codegen pom. Is that
correct, or is the codegen pom copies into source/?
Thanks
--
Ernesto Posse
Zeligsoft
_______________________________________________
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
--
|
Céline JANSSENS
Software Engineer
+33 (0)2 44 47 23 23
|
|
Mail : cej@xxxxxxxxxxx
|
6 rue Léonard De Vinci - BP 0119 - 53001 LAVAL Cedex - FRANCE
www.all4tec.net |
|
_______________________________________________
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
|