camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Christian Müller (JIRA) <j...@apache.org>
Subject [jira] [Commented] (CAMEL-5931) Upgrade Camel features to Spring 3.1 as minimum version
Date Mon, 14 Jan 2013 21:50:13 GMT

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

Christian Müller commented on CAMEL-5931:
-----------------------------------------

Assume Karaf provides a Spring 3.1 and Spring 3.2 feature (in the right way with the same
name and different version numbers).
If we refer to the Spring feature with the version rage you suggest in your patch:
{code}
<feature version='[3.1,4)'>spring</feature>
{code}
I guess Karaf will use Spring 3.2, right?
Because we do not have a Spring 3.2 test set up in Jenkins right now, I think this version
range is to broad. You don't think so?

I will set up a Spring 3.2 build in Jenkins and see how it works.
                
> Upgrade Camel features to Spring 3.1 as minimum version
> -------------------------------------------------------
>
>                 Key: CAMEL-5931
>                 URL: https://issues.apache.org/jira/browse/CAMEL-5931
>             Project: Camel
>          Issue Type: Improvement
>          Components: karaf
>    Affects Versions: 2.11.0
>            Reporter: Claus Ibsen
>            Assignee: Claus Ibsen
>             Fix For: 2.11.0
>
>         Attachments: CAMEL-5931.patch
>
>
> Spring 3.1 is now the default version out of the box. We should have that in Karaf features
as well.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message