You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by "Freeman Fang (JIRA)" <ji...@apache.org> on 2011/09/23 05:17:27 UTC
[jira] [Commented] (CAMEL-4479) Camel-Karaf feature.xml has version
numbers specified too tightly
[ https://issues.apache.org/jira/browse/CAMEL-4479?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13113125#comment-13113125 ]
Freeman Fang commented on CAMEL-4479:
-------------------------------------
Hi,
I believe CAMEL-3995[1] already address the karaf version issue.
And about the commons-pool, I don't see Karaf 2.2.2 kit specify any commons-pool bundle, it's not in karaf 2.2.2 kit by default, do I miss something?
And from camel 2.8.0 we introduce the OBR resolver for camel-karaf features.xml, so if your OSGi container already have mvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.commons-pool/1.5.4_2 then it won't need install org.apache.servicemix.bundles.commons-pool/1.5.4_1.
After you start karaf, you can do
features:install obr //this install obr feature
then
features:addurl mvn:org.apache.camel.karaf/apache-camel/2.8.1/xml/features
features:install camel-jms
Notes: this won't resolve org.apache.servicemix.bundles.commons-pool/1.5.4_1 to org.apache.servicemix.bundles.commons-pool/1.5.4_2, so if your local machine has no org.apache.servicemix.bundles.commons-pool/1.5.4_1 , you need ensure you have a internet connection to download it. It's just that if your OSGi container already have org.apache.servicemix.bundles.commons-pool/1.5.4_2, it won't install org.apache.servicemix.bundles.commons-pool/1.5.4_1 again which keep your bundle list concise and also avoid potential trouble as you described in PAXURL-141
[1]https://issues.apache.org/jira/browse/CAMEL-3995
Freeman
> Camel-Karaf feature.xml has version numbers specified too tightly
> -----------------------------------------------------------------
>
> Key: CAMEL-4479
> URL: https://issues.apache.org/jira/browse/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:
> <repository>mvn:org.apache.karaf.assemblies.features/standard/2.2.0/xml/features</repository>
> which doesn't match my 2.2.2 version and
> <bundle>mvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.commons-pool/1.5.4_1</bundle>
> 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 http://team.ops4j.org/browse/PAXURL-141 "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: http://www.atlassian.com/software/jira