[
https://issues.apache.org/jira/browse/KARAF-2105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13552377#comment-13552377
]
Jean-Baptiste Onofré commented on KARAF-2105:
---------------------------------------------
FYI, I'm working on the Spring 3.2 update (but it requires some "mixing" in
Spring bundles version as 3.2 is not a version available for all Spring
bundles).
> Karaf features for Spring should all be same name and use version ranges
> ------------------------------------------------------------------------
>
> Key: KARAF-2105
> URL: https://issues.apache.org/jira/browse/KARAF-2105
> Project: Karaf
> Issue Type: Improvement
> Components: karaf-feature
> Affects Versions: 2.3.0
> Reporter: Claus Ibsen
> Assignee: Freeman Fang
> Priority: Critical
> Fix For: 2.3.1
>
>
> See
> http://karaf.922171.n3.nabble.com/Apache-Karaf-2-3-And-spring-in-the-out-of-the-box-features-files-tp4027202.html
> The spring features should all be named spring, and use version ranges to
> differentiate between the various spring version supported.
> Currently Spring 3.1 is named spring31, and not spring. This causes problem
> for end users, such as installing both spring 3.0 and 3.1, when they only
> want spring 3.1 etc.
> See more details in that nabble link.
> The ciritical issue is that SMX / Camel etc cannot reuse the spring features
> of Karaf when spring 3.1 is the new default choice.
--
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
