On Fri, Jan 25, 2013 at 9:06 PM, Babak Vahdat <babak.vah...@swissonline.ch> wrote: > Hi > > After the upgrade to Scala 2.10 the build on the CI-Server failed as > apparently it's maven plugin requires minimum Maven 3.0.4+. > > https://builds.apache.org/job/Camel.trunk.notest/1772/console > > However we can't make use of Maven 3.0.4 because of the old issue we have > had with the camel-msv module. Following two relevant old threads we had > about this: > > http://camel.465427.n5.nabble.com/About-Camel-source-which-doesn-t-build-under-Maven-3-0-4-td5517301.html > http://camel.465427.n5.nabble.com/About-latest-build-on-Camel-trunk-fulltest-java7-profile-td5723105.html > > Somehow a catch-22 case… So I went through this to see if we can do better > and found a solution which resolves this old camel-msv module issue > completely even when using Maven 3.0.4 (so now while building no extra > action is required anymore, e.g. delete any potential .m2 cache entry for > org.iso_relax.verifier.jaxp.validation:isorelax-jaxp-bridge:jar:1.0 etc.). > > I also already updated all our relevant Jenkins profiles (trunk 2.10.x > 2.9.x) to make use of "Maven latest" (today that's Maven 3.0.4) instead of > Maven 3.0.3 as I believe this old issue is now definitely fixed. This should > also make camel-scala build happy again. > > Babak
Thanks for the heads up and fixing this. I remember there is a prerequisite option in the root pom.xml where you can set the minimum maven version. Maybe it should be set to 3.0.4 if not already done. > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/HEADS-UP-About-the-newest-failed-build-on-the-CI-Server-tp5726291.html > Sent from the Camel Development mailing list archive at Nabble.com. -- Claus Ibsen ----------------- Red Hat, Inc. FuseSource is now part of Red Hat Email: cib...@redhat.com Web: http://fusesource.com Twitter: davsclaus Blog: http://davsclaus.com Author of Camel in Action: http://www.manning.com/ibsen
