Mailing-List: contact issues-help@karaf.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@karaf.apache.org
Date: Sat, 12 Jan 2013 11:00:13 +0000 (UTC)
From: =?utf-8?Q?Christian_M=C3=BCller_=28JIRA=29?= <jira@apache.org>
To: issues@karaf.apache.org
Message-ID: <JIRA.12626902.1357806250204.124907.1357988413403@arcas>
In-Reply-To: <JIRA.12626902.1357806250204@arcas>
References: <JIRA.12626902.1357806250204@arcas>
Subject: [jira] [Commented] (KARAF-2105) Karaf features for Spring should
 all be same name and use version ranges
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


    [ https://issues.apache.org/jira/browse/KARAF-2105?page=3Dcom.atlassian=
.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D1355=
1888#comment-13551888 ]=20

Christian M=C3=BCller commented on KARAF-2105:
-----------------------------------------

[~ffang]: Thanks for the clarification.
[~davsclaus]: Maybe I misunderstood the comment: "for 3.0.0 we only ship sp=
ring 3.1 so won't have this problem"...
However, as you said, there is a ticket for Spring 3.2 support where we sho=
uld discuss this further.
               =20
> Karaf features for Spring should all be same name and use version ranges
> ------------------------------------------------------------------------
>
>                 Key: KARAF-2105
>                 URL: https://issues.apache.org/jira/browse/KARAF-2105
>             Project: Karaf
>          Issue Type: Improvement
>          Components: karaf-feature
>    Affects Versions: 2.3.0
>            Reporter: Claus Ibsen
>            Assignee: Freeman Fang
>            Priority: Critical
>             Fix For: 2.3.1
>
>
> See
> http://karaf.922171.n3.nabble.com/Apache-Karaf-2-3-And-spring-in-the-out-=
of-the-box-features-files-tp4027202.html
> The spring features should all be named spring, and use version ranges to=
 differentiate between the various spring version supported.
> Currently Spring 3.1 is named spring31, and not spring. This causes probl=
em for end users, such as installing both spring 3.0 and 3.1, when they onl=
y want spring 3.1 etc.
> See more details in that nabble link.
> The ciritical issue is that SMX / Camel etc cannot reuse the spring featu=
res of Karaf when spring 3.1 is the new default choice.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrato=
rs
For more information on JIRA, see: http://www.atlassian.com/software/jira