karaf-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Achim Nierbeck <bcanh...@googlemail.com>
Subject Re: [jira] [Commented] (KARAF-3940) Make it possible / easy to configure which spring version Karaf uses
Date Thu, 20 Aug 2015 09:10:16 GMT
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.

2015-08-20 11:06 GMT+02:00 Claus Ibsen (JIRA) <jira@apache.org>:

>
>     [
> 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)
>



-- 

Apache Member
Apache Karaf <http://karaf.apache.org/> Committer & PMC
OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/> Committer &
Project Lead
blog <http://notizblog.nierbeck.de/>
Co-Author of Apache Karaf Cookbook <http://bit.ly/1ps9rkS>

Software Architect / Project Manager / Scrum Master

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message