[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [papyrus-rt-dev] Failing builds
|
Perhaps the Hudson builds are still using "papyrusrelease" variants of their target platforms? The job configurations would have to be changed to use the "papyrusnightly" variants (there's a system property passsd to maven for that) now that the 0.8 build is complete. The nightly TPs are all lazy.
Christian
On November 9, 2016 at 04:27:50, Peter Cigéhn (peter.cigehn@xxxxxxxxx) wrote:
Hi,
I was planning on
verifying a Bugzilla that Christian have fixed, but we seem to have
yet another similar issue of "pinning" a version of something that
no longer exist. The latest build of
https://hudson.eclipse.org/papyrus-rt/job/Papyrus-RT-Master-Product/
#222 (that I triggered manually, since build #221 had failed
with the mysterious java.io.IOException: Unexpected
termination of the channel) now fails with
Could
not find
"org.eclipse.papyrus.junit.feature.feature.group/2.0.1.201611060311"
in the repositories of the current location
Are we missing a "lazy" keyword here
as well?
/Peter Cigéhn
_______________________________________________
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