[
https://issues.apache.org/jira/browse/KARAF-3940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14704697#comment-14704697
]
Guillaume Nodet commented on KARAF-3940:
----------------------------------------
One possible way would be to flag spring features as dependencies and use some
version range if needed.
That way, the resolver would usually pick up the default one unless a higher
compatible version is specified.
So when a given feature depends on spring, instead of
{code}
<feature version="3.1">spring</feature>
{code}
it should use
{code}
<feature dependency="true" version="[3.1,4)">spring</feature>
{code}
or something like that.
> 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)
