0 Replies Latest reply on Feb 8, 2017 3:57 AM by Davide Cavestro

    Applied rollup1 to Karaf Fuse 6.3: how to avoid rebuilding all artifacts?

    Davide Cavestro Newbie

      I've successfully applied the rollup 1 patch to the whole fabric following the docs: great.

       

      Now I'd like to fix my artifacts configuration in order to avoid having to rebuild them every time I patch/upgrade fuse with a rollup patch.

       

      I've been able to remove most of the unneeded versions from the feature repositories declarations, but I've found no way to avoid tying the features.xml  to a specific version of fuse.

       

      I've tried using the version range syntax from PAX URL, but it always fails unless I specify a specific version:

       

      <repository>mvn:org.apache.camel.karaf/apache-camel//xml/features</repository> <!-- empty version FAILS -->

      <repository>mvn:org.apache.camel.karaf/apache-camel/[2.17.0.redhat-630,]/xml/features</repository> <!-- open range FAILS -->

      <repository>mvn:org.apache.camel.karaf/apache-camel/[2.17.0.redhat-630187,2.17.0.redhat-630999]/xml/features</repository> <!-- delimited range FAILS -->

       

      instead

       

      <repository>mvn:org.apache.camel.karaf/apache-camel/2.17.0.redhat-630224/xml/features</repository> <!-- works -->

       

      I know I could introduce a placeholder, but that's NOT enough, cause in that case I'd have to rebuild again the packages, after tweaking the property with the relevant version every time I want to deploy my bundles on a new version of fuse.

       

      Any idea?