[
https://issues.apache.org/jira/browse/KARAF-3940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14704550#comment-14704550
]
Claus Ibsen commented on KARAF-3940:
------------------------------------
Well something to make it easy for end users to upgrade spring in the current
version of karaf. Today you are locked down on the shipped version, and have to
wait for new release to upgrade.
PS: A bit same problem for jetty. But I guess that one is maybe harder. But
would be nice to just change a version in a .cfg file and restart karaf and its
upgraded.
If the versions is hardcoded in features xml file that are resovled from maven
central its harder to upgrade/change the version. And spring is not 1 bundle so
there are many bundles to upgrade manually and it would be an error prone
procedure.
Maybe there could be a "version alias" config file, so when karaf resolve a
version of a bundle, eg bundle A version 1.2.3, then lookup in the "version
alias" and see if there is a mapping. So you can overrule/control all versions.
> 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)
