camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris Dolan (JIRA)" <>
Subject [jira] [Created] (CAMEL-4479) Camel-Karaf feature.xml has version numbers specified too tightly
Date Thu, 22 Sep 2011 14:58:26 GMT
Camel-Karaf feature.xml has version numbers specified too tightly

                 Key: CAMEL-4479
             Project: Camel
          Issue Type: Bug
          Components: karaf
    Affects Versions: 2.7.0
         Environment: Karaf 2.2.2
            Reporter: Chris Dolan

I'm trying to load activemq-web 5.5.0 into Karaf 2.2.2 via the activemq feature.xml. ActiveMQ
5.5.0 depends on Camel 2.7.0's "camel-jms" feature. The Camel feature.xml has two things that
make it incompatible with Karaf 2.2.2:


which doesn't match my 2.2.2 version and


which does not match the 1.5.4_2 version that is specified by Karaf 2.2.2. Both of these cause
runtime exceptions that prevent loading the feature. In each case, it should be possible (in
theory) to make the Camel feature.xml more flexible my specifying ranges, like "[2.2,3)" or
"[1.5,2)" which would cause pax-url-mvn to look for a match via the Maven metadata.xml. I
haven't actually tested that such a change would work. In my own environment I simply hacked
the XML to put the updated versions, but that's not a sustainable approach.

Part of the problem is "mvn: urls resolve versions
differently from Maven". That defect complains that unadorned versions in mvn: URLs do not
act like usual Maven soft version numbers.

This message is automatically generated by JIRA.
For more information on JIRA, see:


View raw message