[
https://issues.apache.org/jira/browse/KARAF-3940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14704630#comment-14704630
]
Achim Nierbeck commented on KARAF-3940:
---------------------------------------
Sorry replied to the mailinglist instead of posting here:
Jetty is way harder, as it's not really compatible. Especially with minor
version updates and sometimes with patchversions too. Though that should be an
issue of the past. The next thing that interferes with Jetty, each Pax-Web
Version is bound to some Jetty version, or better to some jetty minor version.
For example Pax-Web 4.2.x is bound to jetty 9.2 while Pax-Web 6 is bound to
jetty 9.3 which again needs java8 ... and so on .. so that is a lot harder.
> 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)
