You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@karaf.apache.org by "Jean-Baptiste Onofré (JIRA)" <ji...@apache.org> on 2012/10/15 21:14:03 UTC
[jira] [Commented] (KARAF-1921) Upgrade to Spring 3.1.x for Karaf
2.3.x
[ https://issues.apache.org/jira/browse/KARAF-1921?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13476357#comment-13476357 ]
Jean-Baptiste Onofré commented on KARAF-1921:
---------------------------------------------
I can understand your point. I gonna make some test in Karaf (but also on depending projects) to evaluate the impact.
> Upgrade to Spring 3.1.x for Karaf 2.3.x
> ---------------------------------------
>
> Key: KARAF-1921
> URL: https://issues.apache.org/jira/browse/KARAF-1921
> Project: Karaf
> Issue Type: Bug
> Components: karaf-feature
> Affects Versions: 2.3.0
> Reporter: Hendy Irawan
>
> From the mailing list :
> On Sun, Oct 14, 2012 at 6:59 PM, Christian Schneider [via Karaf] <ml...@n3.nabble.com> wrote:
> I think it depends on how compatible spring 3.1 is. So if we come to the
> conclusion that it should do no harm then we can deliver it of course.
> One way to test this would be a release candidate and give people some
> time to try it and give feedback. If we agree to go this way we should
> deliver the release candidate
> asap so people have maximum time to test. Then shortly before we do the
> 2.3.1 release we can vote if we should deliver spring 3.1 or spring 3.
> Christian
> See: http://karaf.922171.n3.nabble.com/Apache-Karaf-2-3-0-very-close-tp4026295p4026390.html
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira