Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [papyrus-rt-dev] Papyrus-RT Build TP Requires Oxygen Component
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


On Tue, Aug 30, 2016 at 2:44 AM Philip Langer <planger@xxxxxxxxxxxxxxxxx> wrote:
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


On Mon, Aug 29, 2016 at 11:08 PM, Christian Damus <give.a.damus@xxxxxxxxx> wrote:
Hi, again,

As it turns out, the Oxygen version of the Papyrus Developer Tools component is no longer compatible with the Neon stream of the Papyrus Main component, so I had to change the target platform in order for Papyrus-RT to be able to build:


But, in so doing, I had to @Ignore a Papyrus-RT Compare JUnit test case that for some reason was failing in the Gerrit build.  I’ll try to get that reinstated, but I may need help:


Thanks,

Christian



On 29 August, 2016 at 15:12:41, Christian Damus (give.a.damus@xxxxxxxxx) wrote:

Hi, Team,

Papyrus 0.8 (and 1.0) are intended to build and release on a Papyrus Neon.x base, as I understand it.  So, why do the Target Platform used by the build and our Oomph Setup model both use the Papyrus Developer Tools from the Oxygen stream for the JUnit framework?

location "http://hudson.eclipse.org/papyrus/job/Papyrus-Master-Developer/lastSuccessfulBuild/artifact/repository/" eclipse-papyrus-developer-master {

org.eclipse.papyrus.junit.feature.feature.group lazy

}


I would expect this to be pulling the repository from the Papyrus-Neon-Developer build.  This actually broke both the developer environment and Gerrit builds for Papyrus-RT today, because of some churn in bundle versions on Papyrus master branch and the circular dependency problem that we have with this Papyrus Developer component.

Thanks,

Christian



_______________________________________________
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
_______________________________________________
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

Back to the top