Hi, Ernesto,
Yes, the core/tooling/etc. build looks like it is okay now, minus the Compare test that had to be @Ignored. If the codegen build has its own TP that pulls the Papyrus JUnit feature from the Papyrus-Master-Developer build job on Hudson, then it will have to change to use the Papyrus-Neon-Developer job, instead. The Oxygen version of the dev feature is now no longer compatible with Papyrus Neon.
HTH,
Christian On 30 August, 2016 at 13:25:40, Ernesto Posse (eposse@xxxxxxxxxxxxx) wrote:
Our codegen build is also failing with
Cannot satisfy dependency: org.eclipse.papyrus.junit.feature.feature.group 2.0.0.201608300748 depends on: org.eclipse.papyrus.junit.utils [2.0.100.201608300748]
Apparently that also prevents the developer setup from being
installed.
Is there any progress on this?
Thanks
--
Ernesto Posse
Zeligsoft
Hi Christian,
I'm happy to look at the failing Papyrus-RT Compare JUnit test
case (bug 500457). Let me know if you are still on it, to avoid
duplicating the work.
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
|