Ok, great that you have a good handle on it. My face just fell off the bones...
Niclas On Fri, Apr 15, 2016 at 12:46 AM, Paul Merlin <[email protected]> wrote: > Niclas Hedhman a écrit : > > Paul, > > do you have any time to look at this? I am rather uncertain of what the > > intent is and how things work. > In the distributions we ship a maven pom file that allows to "go > offline", that is, download all the Zest SDK dependencies that are not > included in the distributions. We also ship with a gradle file that > allows to do the same thing but this build failure is about maven. > > During the distributions build we assert that this pom works. > But, some builds.a.o agents have different maven versions installed and > some of them have a bug in parsing range versions. It happens that > jClouds has a dependency on a pom that includes range versions. > > In practice this is an intermitent failure as it depends on some buggy > maven versions present on some builds.a.o agent. > > So, nevermind the failure. > > > FWIW, I've reported the problem to jClouds and to the said dependency. > It has been fixed/worked-around upstream since then. But only on > unreleased jClouds 2.0, I'll follow up when the time comes. > > Cheers > > > -- Niclas Hedhman, Software Developer http://zest.apache.org - New Energy for Java
