Hi Christian, Thanks for the hint but I went even one step further and *removed* the <jclouds-feature-version> property!
http://svn.apache.org/viewvc?view=revision&revision=1395123 And as well verified that the karaf features validation is still o.k. In this way we manage the used jclouds version consistently through one *single* maven property which would make life easier. Babak Christian Mueller wrote > Can we also upgrade the jclouds-feature-version to 1.5.1? > > Best, > Christian > > On Sat, Oct 6, 2012 at 9:38 AM, < > bvahdat@ > > wrote: > >> Author: bvahdat >> Date: Sat Oct 6 07:38:15 2012 >> New Revision: 1394954 >> >> URL: http://svn.apache.org/viewvc?rev=1394954&view=rev >> Log: >> Upgrade to JClouds 1.5.1. >> >> Modified: >> camel/trunk/parent/pom.xml >> >> Modified: camel/trunk/parent/pom.xml >> URL: >> http://svn.apache.org/viewvc/camel/trunk/parent/pom.xml?rev=1394954&r1=1394953&r2=1394954&view=diff >> >> ============================================================================== >> --- camel/trunk/parent/pom.xml (original) >> +++ camel/trunk/parent/pom.xml Sat Oct 6 07:38:15 2012 >> @@ -178,7 +178,7 @@ >> > <jaxb-bundle-version> > 2.2.1.1_2 > </jaxb-bundle-version> >> > <jaxen-version> > 1.1.4 > </jaxen-version> >> > <jboss-javaee-6-version> > 1.0.0.Final > </jboss-javaee-6-version> >> - > <jclouds-version> > 1.5.0 > </jclouds-version> >> + > <jclouds-version> > 1.5.1 > </jclouds-version> >> > <jclouds-feature-version> > 1.5.0 > </jclouds-feature-version> >> > <jcr-version> > 2.0 > </jcr-version> >> > <jdom-bundle-version> > 1.1_4 > </jdom-bundle-version> >> >> >> > > > -- -- View this message in context: http://camel.465427.n5.nabble.com/Re-svn-commit-r1394954-camel-trunk-parent-pom-xml-tp5720698p5720702.html Sent from the Camel Development mailing list archive at Nabble.com.
