camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Claus Ibsen (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CAMEL-8007) Camel should not be hardcoded to one specific Karaf release
Date Wed, 03 Dec 2014 19:43:14 GMT

    [ https://issues.apache.org/jira/browse/CAMEL-8007?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14233414#comment-14233414
] 

Claus Ibsen commented on CAMEL-8007:
------------------------------------

Ups that was CXF. Its gone now. So we are not tied to one karaf release.

> Camel should not be hardcoded to one specific Karaf release
> -----------------------------------------------------------
>
>                 Key: CAMEL-8007
>                 URL: https://issues.apache.org/jira/browse/CAMEL-8007
>             Project: Camel
>          Issue Type: Bug
>          Components: karaf
>    Affects Versions: 2.15.0
>            Reporter: Claus Ibsen
>            Priority: Blocker
>             Fix For: 2.15.0
>
>
> Something happened so the features.xml now has a hardcoded karaf version
> This is from the generated source code:
> {code}
> <features xmlns="http://karaf.apache.org/xmlns/features/v1.0.0" name='camel-2.15-SNAPSHOT'>
>   <repository>mvn:org.apache.karaf.assemblies.features/spring/2.4.0/xml/features</repository>
> {code}
> Notice how it says karaf 2.4.0. 
> I suspect it was some spring stuff that was changed. We need to either revert or find
some way for Camel to support Karaf 2.x and 3.x at the same time.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message