Hi I don't see anything strange on this as there was no Hokuspokus I did by the following revision :-)
http://svn.apache.org/viewvc?view=revision&revision=1300914 Through introducing a dedicated <repository> by camel-msv POM we instruct Maven to pick from here: [1] http://svn.apache.org/repos/asf/servicemix/m2-repo/org/iso_relax/verifier/jaxp/validation/isorelax-jaxp-bridge/1.0/isorelax-jaxp-bridge-1.0.pom Instead of here: [2] http://repo.maven.apache.org/maven2/org/iso_relax/verifier/jaxp/validation/isorelax-jaxp-bridge/1.0/isorelax-jaxp-bridge-1.0.pom Now for this to work one should remove any POM which was once already downloaded through [2] IF ANY. From there on Maven will do always download through [1] as we have instructed it to do so. Note that removal of the crappy POM downloaded through [2] should be done ONLY ONCE. Now back to problem with build 124 you've mentioned: I suspect there are other Jenkins Builds for some other Apache projects using the SAME m2-cache on the filesystem causing Maven to poll from [2] as for sure it's not Camel anymore asking for that old POM. I also had the suspection that maybe transitively, we could have the same dependency to isorelax-jaxp-bridge somewhere else through some other Camel modules which makes Maven to poll from [2] which I did already check. This is however not the case. See also the yellow notice here: http://camel.apache.org/building.html Babak Claus Ibsen-2 wrote > > On Tue, Jun 5, 2012 at 5:36 PM, Claus Ibsen <claus.ibsen@> wrote: >> Hi >> >> The Apache CI server on Camel trunk with java7, had an issue at the end. >> I think its related to that Maven 3.0.4 issue with that camel-msv >> component (I think it was that one). >> So I configured it to use Maven 3.0.3 instead, just to see if it >> completes then. >> > > Yes the build was now a success > https://builds.apache.org/job/Camel.trunk.fulltest.java7/125/ > > The next build failed due some internal Hudson issue > (I guess it would be nice if Hudson was improved to better detects its > own failures and display this differently) > https://builds.apache.org/job/Camel.trunk.fulltest.java7/126/ > > I wonder if anyone on the Infra team could remove the below directories? > .m2/repository/org/iso_relax/ > /m2/repository/msv > > As strangely having Maven to re-download the artifact fixes that on Maven > 3.0.4. > Babak provided this workaround in a post on this mailing listing > > > >> >> >> -- >> Claus Ibsen >> ----------------- >> FuseSource >> Email: cibsen@ >> Web: http://fusesource.com >> Twitter: davsclaus, fusenews >> Blog: http://davsclaus.com >> Author of Camel in Action: http://www.manning.com/ibsen > > > > -- > Claus Ibsen > ----------------- > FuseSource > Email: cibsen@ > Web: http://fusesource.com > Twitter: davsclaus, fusenews > Blog: http://davsclaus.com > Author of Camel in Action: http://www.manning.com/ibsen > -- View this message in context: http://camel.465427.n5.nabble.com/DISCUSS-Apache-Camel-2-10-release-tp5691194p5714058.html Sent from the Camel Development mailing list archive at Nabble.com.
