[
https://issues.apache.org/jira/browse/KARAF-3940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14704415#comment-14704415
]
Claus Ibsen commented on KARAF-3940:
------------------------------------
Wonder if a general solution could be to allow to upgrade / change versions
with this command
karaf@root> features:listversions spring
Version Repository Repository URL
[3.1.4.RELEASE ] spring-2.4.3
mvn:org.apache.karaf.assemblies.features/spring/2.4.3/xml/features
[3.2.11.RELEASE_1] spring-2.4.3
mvn:org.apache.karaf.assemblies.features/spring/2.4.3/xml/features
[4.0.7.RELEASE_1 ] spring-2.4.3
mvn:org.apache.karaf.assemblies.features/spring/2.4.3/xml/features
[4.1.6.RELEASE_1 ] spring-2.4.3
mvn:org.apache.karaf.assemblies.features/spring/2.4.3/xml/features
eg have a way of changing the version, so you can say 3.2.11_RELEASE_1 ->
3.2.14_RELEASE_1.
> Make it possible / easy to configure which spring version Karaf uses
> --------------------------------------------------------------------
>
> Key: KARAF-3940
> URL: https://issues.apache.org/jira/browse/KARAF-3940
> Project: Karaf
> Issue Type: Improvement
> Affects Versions: 2.4.3
> Reporter: Claus Ibsen
>
> It would be great if the spring version that karaf uses is configured in one
> of the etc config files. So people can easily upgrade by changing the version
> in that file.
> Today you cannot do that and its a hazzle to upgrade spring. In fact very
> hard as the spring version is hardcoded in the features file
> true mvn:org.apache.karaf.assemblies.features/spring/2.4.3/xml/features
> The reason is that spring has frequent releases and often they have security
> issues in their new releases. Or some 3rd party libraries with osgi ranges
> requires a higher version, even on patch level, eg 3.2.13
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
