Re: Apache Karaf 2.3.0 very close
+1(non-binding) Karaf 2.3.0 - Spring 3.0.x Karaf 3.0 - Spring 3.1 (high priority) Karaf 2.4 - Spring 3.1 (low priority) On Oct 14, 2012, at 11:58 AM, Jean-Baptiste Onofré wrote: > Hi Hendy, > > I don't think it's a good thing to "major" Spring update in a minor Karaf > version. > > If Spring 3.1 is required "quickly", we can provide a Karaf 2.4.x. However, > as already said, we should focus on Karaf 3.0.0 which already provide Spring > 3.1 support (and avoid a 2.4.x branch). > > Regards > JB > > On 10/14/2012 12:38 PM, Hendy Irawan wrote: >> I strongly support Spring 3.1 for future Karaf 2.3.1 :-) >> >> If one requires strictly Spring 3.0, they can still use Karaf 2.3.0 or can >> use "spring30" feature. But I doubt anyone would ever need it (hopefully). >> >> Hendy >> >> >> >> -- >> View this message in context: >> http://karaf.922171.n3.nabble.com/Apache-Karaf-2-3-0-very-close-tp4026295p4026385.html >> Sent from the Karaf - Dev mailing list archive at Nabble.com. > > -- > Jean-Baptiste Onofré > jbono...@apache.org > http://blog.nanthrax.net > Talend - http://www.talend.com
Re: Apache Karaf 2.3.0 very close
Hi Hendy, I don't think it's a good thing to "major" Spring update in a minor Karaf version. If Spring 3.1 is required "quickly", we can provide a Karaf 2.4.x. However, as already said, we should focus on Karaf 3.0.0 which already provide Spring 3.1 support (and avoid a 2.4.x branch). Regards JB On 10/14/2012 12:38 PM, Hendy Irawan wrote: I strongly support Spring 3.1 for future Karaf 2.3.1 :-) If one requires strictly Spring 3.0, they can still use Karaf 2.3.0 or can use "spring30" feature. But I doubt anyone would ever need it (hopefully). Hendy -- View this message in context: http://karaf.922171.n3.nabble.com/Apache-Karaf-2-3-0-very-close-tp4026295p4026385.html Sent from the Karaf - Dev mailing list archive at Nabble.com. -- Jean-Baptiste Onofré jbono...@apache.org http://blog.nanthrax.net Talend - http://www.talend.com
Re: Apache Karaf 2.3.0 very close
Added a JIRA to track : https://issues.apache.org/jira/browse/KARAF-1921 On Sun, Oct 14, 2012 at 6:59 PM, Christian Schneider [via Karaf] < ml-node+s922171n4026390...@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 > > Am 14.10.2012 13:23, schrieb Hendy Irawan: > > > I agree that 2.3.x should be bug fix releases. However Spring 3.1 > inclusion > > isn't intended to fix a bug, merely because Spring 3.0 in Karaf 2.3.0 > was > > an oversight, and that replacing it with Spring 3.1 will do little harm, > if > > any. > > > > Is 2.4 line actually necessary (how much farther can we push old Felix > and > > Servlet 2.5?), or it's just because of Spring... > > > > If so, then I think it's better to direct development to Karaf 3.0 full > > throttle, while 2.3 is the last maintenance/stable line. > > > > Hendy > > > > On Sun, Oct 14, 2012 at 5:56 PM, Christian Schneider [via Karaf] < > > [hidden email] <http://user/SendEmail.jtp?type=node&node=4026390&i=0>> > wrote: > > > >> While we could switch to spring 3.1 in karaf 2.4.0 I think we should > not > >> do it in 2.3.1. > >> > >> The reason is that 2.3.1 will be a bug fix release. So compatibility is > >> the most important thing in these releases. The idea behind this is > that > >> people who need an important e.g. security fix should be able to update > >> karaf without having to retest every deployment. > >> As Spring 3.1 is a minor update not a bugfix update I think the switch > >> should not go into a bugfix release of karaf. > >> > >> We do not really have an official policy like this at karaf but it is > >> how I understand bugfix releases. So what do other think? > >> > >> Christian > >> > >> On 10/14/2012 12:38 PM, Hendy Irawan wrote: > >> > >>> I strongly support Spring 3.1 for future Karaf 2.3.1 :-) > >>> > >>> If one requires strictly Spring 3.0, they can still use Karaf 2.3.0 or > >> can > >>> use "spring30" feature. But I doubt anyone would ever need it > >> (hopefully). > >>> Hendy > >>> > >>> > >>> > >>> -- > >>> View this message in context: > >> > http://karaf.922171.n3.nabble.com/Apache-Karaf-2-3-0-very-close-tp4026295p4026385.html > >>> Sent from the Karaf - Dev mailing list archive at Nabble.com. > >> > >> > >> -- > >> If you reply to this email, your message will be added to the > discussion > >> below: > >> > >> > > >> . > >> NAML< > http://karaf.922171.n3.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml> > > >> > > > > > > > -- > > Christian Schneider > http://www.liquid-reality.de > > Open Source Architect > Talend Application Integration Division http://www.talend.com > > > > -- > If you reply to this email, your message will be added to the discussion > below: > > http://karaf.922171.n3.nabble.com/Apache-Karaf-2-3-0-very-close-tp4026295p4026390.html > To unsubscribe from Apache Karaf 2.3.0 very close, click > here<http://karaf.922171.n3.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=4026295&code=aGVuZHlAc29sdXZhcy5jb218NDAyNjI5NXwxNTI0Njc4NzUy> > . > NAML<http://karaf.922171.n3.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml> > -- Hendy Irawan - on Twitter <http://twitter.com/hendybippo> - on LinkedIn<http://id.linkedin.com/in/hendyirawan> Web Developer | Bippo Indonesia <http://www.bippo.co.id/> | Akselerator Bisnis | Bandung -- View this message in context: http://karaf.922171.n3.nabble.com/Apache-Karaf-2-3-0-very-close-tp4026295p4026393.html Sent from the Karaf - Dev mailing list archive at Nabble.com.
Re: Apache Karaf 2.3.0 very close
I highly support this alternative! :) Using spring 3.1 for 2.3.1-SNAPSHOT and voting before the release would be awesome! :) Hendy On Sun, Oct 14, 2012 at 6:59 PM, Christian Schneider [via Karaf] < ml-node+s922171n4026390...@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 > > Am 14.10.2012 13:23, schrieb Hendy Irawan: > > > I agree that 2.3.x should be bug fix releases. However Spring 3.1 > inclusion > > isn't intended to fix a bug, merely because Spring 3.0 in Karaf 2.3.0 > was > > an oversight, and that replacing it with Spring 3.1 will do little harm, > if > > any. > > > > Is 2.4 line actually necessary (how much farther can we push old Felix > and > > Servlet 2.5?), or it's just because of Spring... > > > > If so, then I think it's better to direct development to Karaf 3.0 full > > throttle, while 2.3 is the last maintenance/stable line. > > > > Hendy > > > > On Sun, Oct 14, 2012 at 5:56 PM, Christian Schneider [via Karaf] < > > [hidden email] <http://user/SendEmail.jtp?type=node&node=4026390&i=0>> > wrote: > > > >> While we could switch to spring 3.1 in karaf 2.4.0 I think we should > not > >> do it in 2.3.1. > >> > >> The reason is that 2.3.1 will be a bug fix release. So compatibility is > >> the most important thing in these releases. The idea behind this is > that > >> people who need an important e.g. security fix should be able to update > >> karaf without having to retest every deployment. > >> As Spring 3.1 is a minor update not a bugfix update I think the switch > >> should not go into a bugfix release of karaf. > >> > >> We do not really have an official policy like this at karaf but it is > >> how I understand bugfix releases. So what do other think? > >> > >> Christian > >> > >> On 10/14/2012 12:38 PM, Hendy Irawan wrote: > >> > >>> I strongly support Spring 3.1 for future Karaf 2.3.1 :-) > >>> > >>> If one requires strictly Spring 3.0, they can still use Karaf 2.3.0 or > >> can > >>> use "spring30" feature. But I doubt anyone would ever need it > >> (hopefully). > >>> Hendy > >>> > >>> > >>> > >>> -- > >>> View this message in context: > >> > http://karaf.922171.n3.nabble.com/Apache-Karaf-2-3-0-very-close-tp4026295p4026385.html > >>> Sent from the Karaf - Dev mailing list archive at Nabble.com. > >> > >> > >> -- > >> If you reply to this email, your message will be added to the > discussion > >> below: > >> > >> > > >> . > >> NAML< > http://karaf.922171.n3.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml> > > >> > > > > > > > -- > > Christian Schneider > http://www.liquid-reality.de > > Open Source Architect > Talend Application Integration Division http://www.talend.com > > > > -- > If you reply to this email, your message will be added to the discussion > below: > > http://karaf.922171.n3.nabble.com/Apache-Karaf-2-3-0-very-close-tp4026295p4026390.html > To unsubscribe from Apache Karaf 2.3.0 very close, click > here<http://karaf.922171.n3.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=4026295&code=aGVuZHlAc29sdXZhcy5jb218NDAyNjI5NXwxNTI0Njc4NzUy> > . > NAML<http://karaf.922171.n3.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml> > -- Hendy Irawan - on Twitter <http://twitter.com/hendybippo> - on LinkedIn<http://id.linkedin.com/in/hendyirawan> Web Developer | Bippo Indonesia <http://www.bippo.co.id/> | Akselerator Bisnis | Bandung -- View this message in context: http://karaf.922171.n3.nabble.com/Apache-Karaf-2-3-0-very-close-tp4026295p4026392.html Sent from the Karaf - Dev mailing list archive at Nabble.com.
Re: Apache Karaf 2.3.0 very close
I think the mid term solution would be to extract spring out of karaf and deliver it separately. The good thing is that karaf itself has no dependency on spring so it should be possible. The issue will be mainly with the products deployed on karaf that then would have to carefully select the correct spring version. Today many applications just depend on feature spring and give no version range. Christian Am 14.10.2012 13:27, schrieb Claus Ibsen: On Sun, Oct 14, 2012 at 12:55 PM, Christian Schneider wrote: While we could switch to spring 3.1 in karaf 2.4.0 I think we should not do it in 2.3.1. The reason is that 2.3.1 will be a bug fix release. So compatibility is the most important thing in these releases. The idea behind this is that people who need an important e.g. security fix should be able to update karaf without having to retest every deployment. As Spring 3.1 is a minor update not a bugfix update I think the switch should not go into a bugfix release of karaf. We do not really have an official policy like this at karaf but it is how I understand bugfix releases. So what do other think? Isn't the point with Karaf that people can assemble the container as they wish/need. So if people need to use Spring 3.1, then IMHO they should be able to do this in Karaf 2.3.x also. Eg as I have said before. Make it easier for people to change the Karaf container to run with Spring 3.1 out of the box. Eg if it can be as easy to change some boot feature to say spring31, instead of spring etc. Or whatever you guys can come up with. Christian On 10/14/2012 12:38 PM, Hendy Irawan wrote: I strongly support Spring 3.1 for future Karaf 2.3.1 :-) If one requires strictly Spring 3.0, they can still use Karaf 2.3.0 or can use "spring30" feature. But I doubt anyone would ever need it (hopefully). Hendy -- View this message in context: http://karaf.922171.n3.nabble.com/Apache-Karaf-2-3-0-very-close-tp4026295p4026385.html Sent from the Karaf - Dev mailing list archive at Nabble.com. -- Christian Schneider http://www.liquid-reality.de Open Source Architect Talend Application Integration Division http://www.talend.com
Re: Apache Karaf 2.3.0 very close
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 Am 14.10.2012 13:23, schrieb Hendy Irawan: I agree that 2.3.x should be bug fix releases. However Spring 3.1 inclusion isn't intended to fix a bug, merely because Spring 3.0 in Karaf 2.3.0 was an oversight, and that replacing it with Spring 3.1 will do little harm, if any. Is 2.4 line actually necessary (how much farther can we push old Felix and Servlet 2.5?), or it's just because of Spring... If so, then I think it's better to direct development to Karaf 3.0 full throttle, while 2.3 is the last maintenance/stable line. Hendy On Sun, Oct 14, 2012 at 5:56 PM, Christian Schneider [via Karaf] < ml-node+s922171n4026387...@n3.nabble.com> wrote: While we could switch to spring 3.1 in karaf 2.4.0 I think we should not do it in 2.3.1. The reason is that 2.3.1 will be a bug fix release. So compatibility is the most important thing in these releases. The idea behind this is that people who need an important e.g. security fix should be able to update karaf without having to retest every deployment. As Spring 3.1 is a minor update not a bugfix update I think the switch should not go into a bugfix release of karaf. We do not really have an official policy like this at karaf but it is how I understand bugfix releases. So what do other think? Christian On 10/14/2012 12:38 PM, Hendy Irawan wrote: I strongly support Spring 3.1 for future Karaf 2.3.1 :-) If one requires strictly Spring 3.0, they can still use Karaf 2.3.0 or can use "spring30" feature. But I doubt anyone would ever need it (hopefully). Hendy -- View this message in context: http://karaf.922171.n3.nabble.com/Apache-Karaf-2-3-0-very-close-tp4026295p4026385.html Sent from the Karaf - Dev mailing list archive at Nabble.com. -- If you reply to this email, your message will be added to the discussion below: http://karaf.922171.n3.nabble.com/Apache-Karaf-2-3-0-very-close-tp4026295p4026387.html To unsubscribe from Apache Karaf 2.3.0 very close, click here<http://karaf.922171.n3.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=4026295&code=aGVuZHlAc29sdXZhcy5jb218NDAyNjI5NXwxNTI0Njc4NzUy> . NAML<http://karaf.922171.n3.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml> -- Christian Schneider http://www.liquid-reality.de Open Source Architect Talend Application Integration Division http://www.talend.com
Re: Apache Karaf 2.3.0 very close
On Sun, Oct 14, 2012 at 12:55 PM, Christian Schneider wrote: > While we could switch to spring 3.1 in karaf 2.4.0 I think we should not do > it in 2.3.1. > > The reason is that 2.3.1 will be a bug fix release. So compatibility is the > most important thing in these releases. The idea behind this is that people > who need an important e.g. security fix should be able to update karaf > without having to retest every deployment. > As Spring 3.1 is a minor update not a bugfix update I think the switch > should not go into a bugfix release of karaf. > > We do not really have an official policy like this at karaf but it is how I > understand bugfix releases. So what do other think? > Isn't the point with Karaf that people can assemble the container as they wish/need. So if people need to use Spring 3.1, then IMHO they should be able to do this in Karaf 2.3.x also. Eg as I have said before. Make it easier for people to change the Karaf container to run with Spring 3.1 out of the box. Eg if it can be as easy to change some boot feature to say spring31, instead of spring etc. Or whatever you guys can come up with. > Christian > > > On 10/14/2012 12:38 PM, Hendy Irawan wrote: >> >> I strongly support Spring 3.1 for future Karaf 2.3.1 :-) >> >> If one requires strictly Spring 3.0, they can still use Karaf 2.3.0 or can >> use "spring30" feature. But I doubt anyone would ever need it (hopefully). >> >> Hendy >> >> >> >> -- >> View this message in context: >> http://karaf.922171.n3.nabble.com/Apache-Karaf-2-3-0-very-close-tp4026295p4026385.html >> Sent from the Karaf - Dev mailing list archive at Nabble.com. > > -- Claus Ibsen - Red Hat, Inc. FuseSource is now part of Red Hat Email: cib...@redhat.com Web: http://fusesource.com Twitter: davsclaus Blog: http://davsclaus.com Author of Camel in Action: http://www.manning.com/ibsen
Re: Apache Karaf 2.3.0 very close
I agree that 2.3.x should be bug fix releases. However Spring 3.1 inclusion isn't intended to fix a bug, merely because Spring 3.0 in Karaf 2.3.0 was an oversight, and that replacing it with Spring 3.1 will do little harm, if any. Is 2.4 line actually necessary (how much farther can we push old Felix and Servlet 2.5?), or it's just because of Spring... If so, then I think it's better to direct development to Karaf 3.0 full throttle, while 2.3 is the last maintenance/stable line. Hendy On Sun, Oct 14, 2012 at 5:56 PM, Christian Schneider [via Karaf] < ml-node+s922171n4026387...@n3.nabble.com> wrote: > While we could switch to spring 3.1 in karaf 2.4.0 I think we should not > do it in 2.3.1. > > The reason is that 2.3.1 will be a bug fix release. So compatibility is > the most important thing in these releases. The idea behind this is that > people who need an important e.g. security fix should be able to update > karaf without having to retest every deployment. > As Spring 3.1 is a minor update not a bugfix update I think the switch > should not go into a bugfix release of karaf. > > We do not really have an official policy like this at karaf but it is > how I understand bugfix releases. So what do other think? > > Christian > > On 10/14/2012 12:38 PM, Hendy Irawan wrote: > > > I strongly support Spring 3.1 for future Karaf 2.3.1 :-) > > > > If one requires strictly Spring 3.0, they can still use Karaf 2.3.0 or > can > > use "spring30" feature. But I doubt anyone would ever need it > (hopefully). > > > > Hendy > > > > > > > > -- > > View this message in context: > http://karaf.922171.n3.nabble.com/Apache-Karaf-2-3-0-very-close-tp4026295p4026385.html > > Sent from the Karaf - Dev mailing list archive at Nabble.com. > > > > -- > If you reply to this email, your message will be added to the discussion > below: > > http://karaf.922171.n3.nabble.com/Apache-Karaf-2-3-0-very-close-tp4026295p4026387.html > To unsubscribe from Apache Karaf 2.3.0 very close, click > here<http://karaf.922171.n3.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=4026295&code=aGVuZHlAc29sdXZhcy5jb218NDAyNjI5NXwxNTI0Njc4NzUy> > . > NAML<http://karaf.922171.n3.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml> > -- Hendy Irawan - on Twitter <http://twitter.com/hendybippo> - on LinkedIn<http://id.linkedin.com/in/hendyirawan> Web Developer | Bippo Indonesia <http://www.bippo.co.id/> | Akselerator Bisnis | Bandung -- View this message in context: http://karaf.922171.n3.nabble.com/Apache-Karaf-2-3-0-very-close-tp4026295p4026388.html Sent from the Karaf - Dev mailing list archive at Nabble.com.
Re: Apache Karaf 2.3.0 very close
While we could switch to spring 3.1 in karaf 2.4.0 I think we should not do it in 2.3.1. The reason is that 2.3.1 will be a bug fix release. So compatibility is the most important thing in these releases. The idea behind this is that people who need an important e.g. security fix should be able to update karaf without having to retest every deployment. As Spring 3.1 is a minor update not a bugfix update I think the switch should not go into a bugfix release of karaf. We do not really have an official policy like this at karaf but it is how I understand bugfix releases. So what do other think? Christian On 10/14/2012 12:38 PM, Hendy Irawan wrote: I strongly support Spring 3.1 for future Karaf 2.3.1 :-) If one requires strictly Spring 3.0, they can still use Karaf 2.3.0 or can use "spring30" feature. But I doubt anyone would ever need it (hopefully). Hendy -- View this message in context: http://karaf.922171.n3.nabble.com/Apache-Karaf-2-3-0-very-close-tp4026295p4026385.html Sent from the Karaf - Dev mailing list archive at Nabble.com.
Re: Apache Karaf 2.3.0 very close
I strongly support Spring 3.1 for future Karaf 2.3.1 :-) If one requires strictly Spring 3.0, they can still use Karaf 2.3.0 or can use "spring30" feature. But I doubt anyone would ever need it (hopefully). Hendy -- View this message in context: http://karaf.922171.n3.nabble.com/Apache-Karaf-2-3-0-very-close-tp4026295p4026385.html Sent from the Karaf - Dev mailing list archive at Nabble.com.
Re: Apache Karaf 2.3.0 very close
oh, pretty late but still: definitely +1 for timed releases :-) Kind regards, Andreas On Thu, Oct 11, 2012 at 6:58 PM, Jamie G. wrote: > With the last of the karaf 2.3.0 issues marked as resolved, I'm > setting things up for a RC build candidate. > > Cheers, > Jamie > > On Thu, Oct 11, 2012 at 11:14 AM, Heath Kesler wrote: >> Hi JB, >> >> +1 from me >> >> Cheers, Heath >> >> On Oct 10, 2012, at 2:10 AM, Achim Nierbeck wrote: >> >>> Hi JB, >>> >>> +1 on all points :) >>> >>> regards, Achim >>> >>> 2012/10/10 Jean-Baptiste Onofré : >>>> Hi guys, >>>> >>>> just an summarise and "close" the discussion. >>>> >>>> Regarding the different message, the final proposal is: >>>> >>>> - stay with Spring 3.0.x and Jetty 7.6.x in Karaf 2.3.0 >>>> - depending of the effort, include an optional spring31 feature in Karaf >>>> 2.3.0 (I'm working on it and I will give you an update) >>>> >>>> Regarding Karaf 2.4.x, we can start a discussion thread but I don't think >>>> it's a good idea: Karaf 3.0.0 already includes Spring 3.1.x and Jetty 8.x, >>>> I >>>> think it makes sense to focus on this release more than an intermediate >>>> one. >>>> >>>> Karaf 2.3.0 should be released tonight. >>>> >>>> Does it work for all ? >>>> >>>> Regards >>>> JB >>>> >>>> >>>> On 10/08/2012 09:38 AM, j...@nanthrax.net wrote: >>>>> >>>>> Great, thanks a lot ! >>>>> >>>>> -- >>>>> Jean-Baptiste Onofré >>>>> jbono...@apache.org >>>>> http://blog.nanthrax.net >>>>> Talend - http://wwx.talend.com >>>>> >>>>> - Reply message - >>>>> From: "Andreas Pieber" >>>>> To: >>>>> Subject: Apache Karaf 2.3.0 very close >>>>> Date: Mon, Oct 8, 2012 9:17 am >>>>> >>>>> >>>>> Hey, >>>>> >>>>> On Mon, Oct 8, 2012 at 7:46 AM, Jean-Baptiste Onofré >>>>> wrote: >>>>>> >>>>>> @Andreas, could you take a look on KARAF-1878 and KARAF-1752 (assigned to >>>>>> you) ? If you are busy today, I think we can postpone to 2.3.1. >>>>> >>>>> >>>>> I wanted to keep KARAF-1878 opened for review till tonight; I'll apply >>>>> afterwards. I'll also apply KARAF-1752 then. >>>>> >>>>> Kind regards, >>>>> Andreas >>>>> >>>>>> >>>>>> Thanks all guys, >>>>>> Regards >>>>>> JB >>>>>> -- >>>>>> Jean-Baptiste Onofré >>>>>> jbono...@apache.org >>>>>> http://blog.nanthrax.net >>>>>> Talend - http://www.talend.com >>>> >>>> >>>> -- >>>> Jean-Baptiste Onofré >>>> jbono...@apache.org >>>> http://blog.nanthrax.net >>>> Talend - http://www.talend.com >>> >>> >>> >>> -- >>> >>> Apache Karaf <http://karaf.apache.org/> Committer & PMC >>> OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/> >>> Committer & Project Lead >>> OPS4J Pax for Vaadin >>> <http://team.ops4j.org/wiki/display/PAXVAADIN/Home> Commiter & Project >>> Lead >>> blog <http://notizblog.nierbeck.de/> >>
Re: Apache Karaf 2.3.0 very close
With the last of the karaf 2.3.0 issues marked as resolved, I'm setting things up for a RC build candidate. Cheers, Jamie On Thu, Oct 11, 2012 at 11:14 AM, Heath Kesler wrote: > Hi JB, > > +1 from me > > Cheers, Heath > > On Oct 10, 2012, at 2:10 AM, Achim Nierbeck wrote: > >> Hi JB, >> >> +1 on all points :) >> >> regards, Achim >> >> 2012/10/10 Jean-Baptiste Onofré : >>> Hi guys, >>> >>> just an summarise and "close" the discussion. >>> >>> Regarding the different message, the final proposal is: >>> >>> - stay with Spring 3.0.x and Jetty 7.6.x in Karaf 2.3.0 >>> - depending of the effort, include an optional spring31 feature in Karaf >>> 2.3.0 (I'm working on it and I will give you an update) >>> >>> Regarding Karaf 2.4.x, we can start a discussion thread but I don't think >>> it's a good idea: Karaf 3.0.0 already includes Spring 3.1.x and Jetty 8.x, I >>> think it makes sense to focus on this release more than an intermediate one. >>> >>> Karaf 2.3.0 should be released tonight. >>> >>> Does it work for all ? >>> >>> Regards >>> JB >>> >>> >>> On 10/08/2012 09:38 AM, j...@nanthrax.net wrote: >>>> >>>> Great, thanks a lot ! >>>> >>>> -- >>>> Jean-Baptiste Onofré >>>> jbono...@apache.org >>>> http://blog.nanthrax.net >>>> Talend - http://wwx.talend.com >>>> >>>> - Reply message - >>>> From: "Andreas Pieber" >>>> To: >>>> Subject: Apache Karaf 2.3.0 very close >>>> Date: Mon, Oct 8, 2012 9:17 am >>>> >>>> >>>> Hey, >>>> >>>> On Mon, Oct 8, 2012 at 7:46 AM, Jean-Baptiste Onofré >>>> wrote: >>>>> >>>>> @Andreas, could you take a look on KARAF-1878 and KARAF-1752 (assigned to >>>>> you) ? If you are busy today, I think we can postpone to 2.3.1. >>>> >>>> >>>> I wanted to keep KARAF-1878 opened for review till tonight; I'll apply >>>> afterwards. I'll also apply KARAF-1752 then. >>>> >>>> Kind regards, >>>> Andreas >>>> >>>>> >>>>> Thanks all guys, >>>>> Regards >>>>> JB >>>>> -- >>>>> Jean-Baptiste Onofré >>>>> jbono...@apache.org >>>>> http://blog.nanthrax.net >>>>> Talend - http://www.talend.com >>> >>> >>> -- >>> Jean-Baptiste Onofré >>> jbono...@apache.org >>> http://blog.nanthrax.net >>> Talend - http://www.talend.com >> >> >> >> -- >> >> Apache Karaf <http://karaf.apache.org/> Committer & PMC >> OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/> >> Committer & Project Lead >> OPS4J Pax for Vaadin >> <http://team.ops4j.org/wiki/display/PAXVAADIN/Home> Commiter & Project >> Lead >> blog <http://notizblog.nierbeck.de/> >
Re: Apache Karaf 2.3.0 very close
Hi JB, +1 from me Cheers, Heath On Oct 10, 2012, at 2:10 AM, Achim Nierbeck wrote: > Hi JB, > > +1 on all points :) > > regards, Achim > > 2012/10/10 Jean-Baptiste Onofré : >> Hi guys, >> >> just an summarise and "close" the discussion. >> >> Regarding the different message, the final proposal is: >> >> - stay with Spring 3.0.x and Jetty 7.6.x in Karaf 2.3.0 >> - depending of the effort, include an optional spring31 feature in Karaf >> 2.3.0 (I'm working on it and I will give you an update) >> >> Regarding Karaf 2.4.x, we can start a discussion thread but I don't think >> it's a good idea: Karaf 3.0.0 already includes Spring 3.1.x and Jetty 8.x, I >> think it makes sense to focus on this release more than an intermediate one. >> >> Karaf 2.3.0 should be released tonight. >> >> Does it work for all ? >> >> Regards >> JB >> >> >> On 10/08/2012 09:38 AM, j...@nanthrax.net wrote: >>> >>> Great, thanks a lot ! >>> >>> -- >>> Jean-Baptiste Onofré >>> jbono...@apache.org >>> http://blog.nanthrax.net >>> Talend - http://wwx.talend.com >>> >>> - Reply message - >>> From: "Andreas Pieber" >>> To: >>> Subject: Apache Karaf 2.3.0 very close >>> Date: Mon, Oct 8, 2012 9:17 am >>> >>> >>> Hey, >>> >>> On Mon, Oct 8, 2012 at 7:46 AM, Jean-Baptiste Onofré >>> wrote: >>>> >>>> @Andreas, could you take a look on KARAF-1878 and KARAF-1752 (assigned to >>>> you) ? If you are busy today, I think we can postpone to 2.3.1. >>> >>> >>> I wanted to keep KARAF-1878 opened for review till tonight; I'll apply >>> afterwards. I'll also apply KARAF-1752 then. >>> >>> Kind regards, >>> Andreas >>> >>>> >>>> Thanks all guys, >>>> Regards >>>> JB >>>> -- >>>> Jean-Baptiste Onofré >>>> jbono...@apache.org >>>> http://blog.nanthrax.net >>>> Talend - http://www.talend.com >> >> >> -- >> Jean-Baptiste Onofré >> jbono...@apache.org >> http://blog.nanthrax.net >> Talend - http://www.talend.com > > > > -- > > Apache Karaf <http://karaf.apache.org/> Committer & PMC > OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/> > Committer & Project Lead > OPS4J Pax for Vaadin > <http://team.ops4j.org/wiki/display/PAXVAADIN/Home> Commiter & Project > Lead > blog <http://notizblog.nierbeck.de/>
Re: Apache Karaf 2.3.0 very close
Fully agree, as I said on IRC: cschneide, anierbeck: all is already there in 3.0: it looks stable for me, Jetty 8 is there, Spring 3.1 is there cschneide, anierbeck: with some "effort" we can provide a 3.0.0 quickly I think So we are in line ;) Regards JB On 10/11/2012 10:59 AM, Achim Nierbeck wrote: Hi JB, I'm fine with a 3.1 specific feature, so if people really want to use it in the 2.x line they need to make sure they do get the right one. Besides that I'd prefer that we get 3.0 out asap instead of fumbling with a 2.4 release regards, Achim 2012/10/11 Jean-Baptiste Onofré : Hi guys, just an update about this discussion. I added spring31* features in Karaf 2.3.x. I don't want to add spring*/3.1.2.RELEASE features, as it will be used by default (for instance, if a feature uses a spring version range like [3,4), by default, spring 3.1.2.RELEASE would be installed). So, to prevent potential side effect, I have clearly identified the features with 31 in the name (spring31, spring31-jms, etc). The issue with this approach is that, if a feature wants to use spring 3.1, it should rely on a specific name, which is not perfect. So I wonder if it doesn't make sense to simply remove spring 3.1.x features in Karaf 2.3.0 and wait for Karaf 3.0.0 release (which includes it), or if we *really* need Spring 3.1 support quickly prepare Karaf 2.4.0 which can be exactly the same as Karaf 2.3.0 but with the upgrades to Spring 3.1 and Jetty 8 for instance. WDYT ? Regards JB On 10/10/2012 08:05 AM, Jean-Baptiste Onofré wrote: Hi guys, just an summarise and "close" the discussion. Regarding the different message, the final proposal is: - stay with Spring 3.0.x and Jetty 7.6.x in Karaf 2.3.0 - depending of the effort, include an optional spring31 feature in Karaf 2.3.0 (I'm working on it and I will give you an update) Regarding Karaf 2.4.x, we can start a discussion thread but I don't think it's a good idea: Karaf 3.0.0 already includes Spring 3.1.x and Jetty 8.x, I think it makes sense to focus on this release more than an intermediate one. Karaf 2.3.0 should be released tonight. Does it work for all ? Regards JB On 10/08/2012 09:38 AM, j...@nanthrax.net wrote: Great, thanks a lot ! -- Jean-Baptiste Onofré jbono...@apache.org http://blog.nanthrax.net Talend - http://wwx.talend.com - Reply message ----- From: "Andreas Pieber" To: Subject: Apache Karaf 2.3.0 very close Date: Mon, Oct 8, 2012 9:17 am Hey, On Mon, Oct 8, 2012 at 7:46 AM, Jean-Baptiste Onofré wrote: @Andreas, could you take a look on KARAF-1878 and KARAF-1752 (assigned to you) ? If you are busy today, I think we can postpone to 2.3.1. I wanted to keep KARAF-1878 opened for review till tonight; I'll apply afterwards. I'll also apply KARAF-1752 then. Kind regards, Andreas Thanks all guys, Regards JB -- Jean-Baptiste Onofré jbono...@apache.org http://blog.nanthrax.net Talend - http://www.talend.com -- Jean-Baptiste Onofré jbono...@apache.org http://blog.nanthrax.net Talend - http://www.talend.com -- Jean-Baptiste Onofré jbono...@apache.org http://blog.nanthrax.net Talend - http://www.talend.com
Re: Apache Karaf 2.3.0 very close
+1 I am pretty sure we can release karaf 3.0.0 rc1 pretty soon. Christian On 10/11/2012 10:44 AM, Jean-Baptiste Onofré wrote: Hi guys, just an update about this discussion. I added spring31* features in Karaf 2.3.x. I don't want to add spring*/3.1.2.RELEASE features, as it will be used by default (for instance, if a feature uses a spring version range like [3,4), by default, spring 3.1.2.RELEASE would be installed). So, to prevent potential side effect, I have clearly identified the features with 31 in the name (spring31, spring31-jms, etc). The issue with this approach is that, if a feature wants to use spring 3.1, it should rely on a specific name, which is not perfect. So I wonder if it doesn't make sense to simply remove spring 3.1.x features in Karaf 2.3.0 and wait for Karaf 3.0.0 release (which includes it), or if we *really* need Spring 3.1 support quickly prepare Karaf 2.4.0 which can be exactly the same as Karaf 2.3.0 but with the upgrades to Spring 3.1 and Jetty 8 for instance. WDYT ? Regards JB On 10/10/2012 08:05 AM, Jean-Baptiste Onofré wrote: Hi guys, just an summarise and "close" the discussion. Regarding the different message, the final proposal is: - stay with Spring 3.0.x and Jetty 7.6.x in Karaf 2.3.0 - depending of the effort, include an optional spring31 feature in Karaf 2.3.0 (I'm working on it and I will give you an update) Regarding Karaf 2.4.x, we can start a discussion thread but I don't think it's a good idea: Karaf 3.0.0 already includes Spring 3.1.x and Jetty 8.x, I think it makes sense to focus on this release more than an intermediate one. Karaf 2.3.0 should be released tonight. Does it work for all ? Regards JB On 10/08/2012 09:38 AM, j...@nanthrax.net wrote: Great, thanks a lot ! -- Jean-Baptiste Onofré jbono...@apache.org http://blog.nanthrax.net Talend - http://wwx.talend.com - Reply message - From: "Andreas Pieber" To: Subject: Apache Karaf 2.3.0 very close Date: Mon, Oct 8, 2012 9:17 am Hey, On Mon, Oct 8, 2012 at 7:46 AM, Jean-Baptiste Onofré wrote: @Andreas, could you take a look on KARAF-1878 and KARAF-1752 (assigned to you) ? If you are busy today, I think we can postpone to 2.3.1. I wanted to keep KARAF-1878 opened for review till tonight; I'll apply afterwards. I'll also apply KARAF-1752 then. Kind regards, Andreas Thanks all guys, Regards JB -- Jean-Baptiste Onofré jbono...@apache.org http://blog.nanthrax.net Talend - http://www.talend.com
Re: Apache Karaf 2.3.0 very close
Hi JB, I'm fine with a 3.1 specific feature, so if people really want to use it in the 2.x line they need to make sure they do get the right one. Besides that I'd prefer that we get 3.0 out asap instead of fumbling with a 2.4 release regards, Achim 2012/10/11 Jean-Baptiste Onofré : > Hi guys, > > just an update about this discussion. > > I added spring31* features in Karaf 2.3.x. > > I don't want to add spring*/3.1.2.RELEASE features, as it will be used by > default (for instance, if a feature uses a spring version range like [3,4), > by default, spring 3.1.2.RELEASE would be installed). So, to prevent > potential side effect, I have clearly identified the features with 31 in the > name (spring31, spring31-jms, etc). > > The issue with this approach is that, if a feature wants to use spring 3.1, > it should rely on a specific name, which is not perfect. > > So I wonder if it doesn't make sense to simply remove spring 3.1.x features > in Karaf 2.3.0 and wait for Karaf 3.0.0 release (which includes it), or if > we *really* need Spring 3.1 support quickly prepare Karaf 2.4.0 which can be > exactly the same as Karaf 2.3.0 but with the upgrades to Spring 3.1 and > Jetty 8 for instance. > > WDYT ? > > Regards > JB > > > On 10/10/2012 08:05 AM, Jean-Baptiste Onofré wrote: >> >> Hi guys, >> >> just an summarise and "close" the discussion. >> >> Regarding the different message, the final proposal is: >> >> - stay with Spring 3.0.x and Jetty 7.6.x in Karaf 2.3.0 >> - depending of the effort, include an optional spring31 feature in Karaf >> 2.3.0 (I'm working on it and I will give you an update) >> >> Regarding Karaf 2.4.x, we can start a discussion thread but I don't >> think it's a good idea: Karaf 3.0.0 already includes Spring 3.1.x and >> Jetty 8.x, I think it makes sense to focus on this release more than an >> intermediate one. >> >> Karaf 2.3.0 should be released tonight. >> >> Does it work for all ? >> >> Regards >> JB >> >> On 10/08/2012 09:38 AM, j...@nanthrax.net wrote: >>> >>> Great, thanks a lot ! >>> >>> -- >>> Jean-Baptiste Onofré >>> jbono...@apache.org >>> http://blog.nanthrax.net >>> Talend - http://wwx.talend.com >>> >>> - Reply message - >>> From: "Andreas Pieber" >>> To: >>> Subject: Apache Karaf 2.3.0 very close >>> Date: Mon, Oct 8, 2012 9:17 am >>> >>> >>> Hey, >>> >>> On Mon, Oct 8, 2012 at 7:46 AM, Jean-Baptiste Onofré >>> wrote: >>>> >>>> @Andreas, could you take a look on KARAF-1878 and KARAF-1752 >>>> (assigned to >>>> you) ? If you are busy today, I think we can postpone to 2.3.1. >>> >>> >>> I wanted to keep KARAF-1878 opened for review till tonight; I'll apply >>> afterwards. I'll also apply KARAF-1752 then. >>> >>> Kind regards, >>> Andreas >>> >>>> >>>> Thanks all guys, >>>> Regards >>>> JB >>>> -- >>>> Jean-Baptiste Onofré >>>> jbono...@apache.org >>>> http://blog.nanthrax.net >>>> Talend - http://www.talend.com >> >> > > -- > Jean-Baptiste Onofré > jbono...@apache.org > http://blog.nanthrax.net > Talend - http://www.talend.com -- Apache Karaf <http://karaf.apache.org/> Committer & PMC OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/> Committer & Project Lead OPS4J Pax for Vaadin <http://team.ops4j.org/wiki/display/PAXVAADIN/Home> Commiter & Project Lead blog <http://notizblog.nierbeck.de/>
Re: Apache Karaf 2.3.0 very close
Hi guys, just an update about this discussion. I added spring31* features in Karaf 2.3.x. I don't want to add spring*/3.1.2.RELEASE features, as it will be used by default (for instance, if a feature uses a spring version range like [3,4), by default, spring 3.1.2.RELEASE would be installed). So, to prevent potential side effect, I have clearly identified the features with 31 in the name (spring31, spring31-jms, etc). The issue with this approach is that, if a feature wants to use spring 3.1, it should rely on a specific name, which is not perfect. So I wonder if it doesn't make sense to simply remove spring 3.1.x features in Karaf 2.3.0 and wait for Karaf 3.0.0 release (which includes it), or if we *really* need Spring 3.1 support quickly prepare Karaf 2.4.0 which can be exactly the same as Karaf 2.3.0 but with the upgrades to Spring 3.1 and Jetty 8 for instance. WDYT ? Regards JB On 10/10/2012 08:05 AM, Jean-Baptiste Onofré wrote: Hi guys, just an summarise and "close" the discussion. Regarding the different message, the final proposal is: - stay with Spring 3.0.x and Jetty 7.6.x in Karaf 2.3.0 - depending of the effort, include an optional spring31 feature in Karaf 2.3.0 (I'm working on it and I will give you an update) Regarding Karaf 2.4.x, we can start a discussion thread but I don't think it's a good idea: Karaf 3.0.0 already includes Spring 3.1.x and Jetty 8.x, I think it makes sense to focus on this release more than an intermediate one. Karaf 2.3.0 should be released tonight. Does it work for all ? Regards JB On 10/08/2012 09:38 AM, j...@nanthrax.net wrote: Great, thanks a lot ! -- Jean-Baptiste Onofré jbono...@apache.org http://blog.nanthrax.net Talend - http://wwx.talend.com - Reply message - From: "Andreas Pieber" To: Subject: Apache Karaf 2.3.0 very close Date: Mon, Oct 8, 2012 9:17 am Hey, On Mon, Oct 8, 2012 at 7:46 AM, Jean-Baptiste Onofré wrote: @Andreas, could you take a look on KARAF-1878 and KARAF-1752 (assigned to you) ? If you are busy today, I think we can postpone to 2.3.1. I wanted to keep KARAF-1878 opened for review till tonight; I'll apply afterwards. I'll also apply KARAF-1752 then. Kind regards, Andreas Thanks all guys, Regards JB -- Jean-Baptiste Onofré jbono...@apache.org http://blog.nanthrax.net Talend - http://www.talend.com -- Jean-Baptiste Onofré jbono...@apache.org http://blog.nanthrax.net Talend - http://www.talend.com
Re: Apache Karaf 2.3.0 very close
+1 Keep us posted how the optional spring31 feature work... Thanks, Christian On Wed, Oct 10, 2012 at 8:05 AM, Jean-Baptiste Onofré wrote: > Hi guys, > > just an summarise and "close" the discussion. > > Regarding the different message, the final proposal is: > > - stay with Spring 3.0.x and Jetty 7.6.x in Karaf 2.3.0 > - depending of the effort, include an optional spring31 feature in Karaf > 2.3.0 (I'm working on it and I will give you an update) > > Regarding Karaf 2.4.x, we can start a discussion thread but I don't think > it's a good idea: Karaf 3.0.0 already includes Spring 3.1.x and Jetty 8.x, > I think it makes sense to focus on this release more than an intermediate > one. > > Karaf 2.3.0 should be released tonight. > > Does it work for all ? > > Regards > JB > > > On 10/08/2012 09:38 AM, j...@nanthrax.net wrote: > >> Great, thanks a lot ! >> >> -- >> Jean-Baptiste Onofré >> jbono...@apache.org >> http://blog.nanthrax.net >> Talend - http://wwx.talend.com >> >> - Reply message - >> From: "Andreas Pieber" >> To: >> Subject: Apache Karaf 2.3.0 very close >> Date: Mon, Oct 8, 2012 9:17 am >> >> >> Hey, >> >> On Mon, Oct 8, 2012 at 7:46 AM, Jean-Baptiste Onofré >> wrote: >> >>> @Andreas, could you take a look on KARAF-1878 and KARAF-1752 (assigned to >>> you) ? If you are busy today, I think we can postpone to 2.3.1. >>> >> >> I wanted to keep KARAF-1878 opened for review till tonight; I'll apply >> afterwards. I'll also apply KARAF-1752 then. >> >> Kind regards, >> Andreas >> >> >>> Thanks all guys, >>> Regards >>> JB >>> -- >>> Jean-Baptiste Onofré >>> jbono...@apache.org >>> http://blog.nanthrax.net >>> Talend - http://www.talend.com >>> >> > -- > Jean-Baptiste Onofré > jbono...@apache.org > http://blog.nanthrax.net > Talend - http://www.talend.com > --
Re: Apache Karaf 2.3.0 very close
I agree with JB at all points. I feel that holding back 2.3 in favor of 3.0.0 was a bad idea and I wouldn't want to see the same happening to future 2.x versions. If there is need for a 2.4 let's get it done regardless of when we'll do 3.0.0. -- *Ioannis Canellos* * ** Blog: http://iocanel.blogspot.com ** Twitter: iocanel *
Re: Apache Karaf 2.3.0 very close
Hi JB, +1 on all points :) regards, Achim 2012/10/10 Jean-Baptiste Onofré : > Hi guys, > > just an summarise and "close" the discussion. > > Regarding the different message, the final proposal is: > > - stay with Spring 3.0.x and Jetty 7.6.x in Karaf 2.3.0 > - depending of the effort, include an optional spring31 feature in Karaf > 2.3.0 (I'm working on it and I will give you an update) > > Regarding Karaf 2.4.x, we can start a discussion thread but I don't think > it's a good idea: Karaf 3.0.0 already includes Spring 3.1.x and Jetty 8.x, I > think it makes sense to focus on this release more than an intermediate one. > > Karaf 2.3.0 should be released tonight. > > Does it work for all ? > > Regards > JB > > > On 10/08/2012 09:38 AM, j...@nanthrax.net wrote: >> >> Great, thanks a lot ! >> >> -- >> Jean-Baptiste Onofré >> jbono...@apache.org >> http://blog.nanthrax.net >> Talend - http://wwx.talend.com >> >> - Reply message - >> From: "Andreas Pieber" >> To: >> Subject: Apache Karaf 2.3.0 very close >> Date: Mon, Oct 8, 2012 9:17 am >> >> >> Hey, >> >> On Mon, Oct 8, 2012 at 7:46 AM, Jean-Baptiste Onofré >> wrote: >>> >>> @Andreas, could you take a look on KARAF-1878 and KARAF-1752 (assigned to >>> you) ? If you are busy today, I think we can postpone to 2.3.1. >> >> >> I wanted to keep KARAF-1878 opened for review till tonight; I'll apply >> afterwards. I'll also apply KARAF-1752 then. >> >> Kind regards, >> Andreas >> >>> >>> Thanks all guys, >>> Regards >>> JB >>> -- >>> Jean-Baptiste Onofré >>> jbono...@apache.org >>> http://blog.nanthrax.net >>> Talend - http://www.talend.com > > > -- > Jean-Baptiste Onofré > jbono...@apache.org > http://blog.nanthrax.net > Talend - http://www.talend.com -- Apache Karaf <http://karaf.apache.org/> Committer & PMC OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/> Committer & Project Lead OPS4J Pax for Vaadin <http://team.ops4j.org/wiki/display/PAXVAADIN/Home> Commiter & Project Lead blog <http://notizblog.nierbeck.de/>
Re: Apache Karaf 2.3.0 very close
Hi guys, just an summarise and "close" the discussion. Regarding the different message, the final proposal is: - stay with Spring 3.0.x and Jetty 7.6.x in Karaf 2.3.0 - depending of the effort, include an optional spring31 feature in Karaf 2.3.0 (I'm working on it and I will give you an update) Regarding Karaf 2.4.x, we can start a discussion thread but I don't think it's a good idea: Karaf 3.0.0 already includes Spring 3.1.x and Jetty 8.x, I think it makes sense to focus on this release more than an intermediate one. Karaf 2.3.0 should be released tonight. Does it work for all ? Regards JB On 10/08/2012 09:38 AM, j...@nanthrax.net wrote: Great, thanks a lot ! -- Jean-Baptiste Onofré jbono...@apache.org http://blog.nanthrax.net Talend - http://wwx.talend.com - Reply message - From: "Andreas Pieber" To: Subject: Apache Karaf 2.3.0 very close Date: Mon, Oct 8, 2012 9:17 am Hey, On Mon, Oct 8, 2012 at 7:46 AM, Jean-Baptiste Onofré wrote: @Andreas, could you take a look on KARAF-1878 and KARAF-1752 (assigned to you) ? If you are busy today, I think we can postpone to 2.3.1. I wanted to keep KARAF-1878 opened for review till tonight; I'll apply afterwards. I'll also apply KARAF-1752 then. Kind regards, Andreas Thanks all guys, Regards JB -- Jean-Baptiste Onofré jbono...@apache.org http://blog.nanthrax.net Talend - http://www.talend.com -- Jean-Baptiste Onofré jbono...@apache.org http://blog.nanthrax.net Talend - http://www.talend.com
Re: Apache Karaf 2.3.0 very close
w it's again a pain to find it. >>>>>>> >>>>>>> I think we need to redo our webpage desperately since not all >>>>>>> information can be found easily and the menu >>>>>>> doesn't necessarily relate to the content (e.g. the manual) >>>>>>> >>>>>>> regards, Achim >>>>>>> >>>>>>> 2012/10/9 Charles Moulliard : >>>>>>>> Even if I understand the karaf position I completely agree about >>>>> Claus's >>>>>>>> remark to also have Spring 3.1 for Camel and others projects. >>>>>>>> >>>>>>>> What I would like to propose is that we create for Karaf/ServiceMix >>>>>>>> projects a page containing a table of the different software used and >>>>>>> have >>>>>>>> a roadmap about them. This question is important not only for Spring >>>>>>>> framework but also Pax, Aries, Felix, ... which are (re)packaged into >>>>>>>> Karaf/ServiceMix >>>>>>>> This will avoid that we discover a few days before the publication of >>>>> a >>>>>>>> release that we have miss something >>>>>>>> >>>>>>>> Just my 5€ cents. >>>>>>>> >>>>>>>> On Tue, Oct 9, 2012 at 8:19 AM, Claus Ibsen >>>>>>> wrote: >>>>>>>> >>>>>>>>> On Mon, Oct 8, 2012 at 7:30 PM, Daniel Kulp >>>>> wrote: >>>>>>>>>> >>>>>>>>>> On Oct 8, 2012, at 1:08 PM, Jean-Baptiste Onofré >>>>>>>>> wrote: >>>>>>>>>> >>>>>>>>>>> Agree Claus, but Camel is not the only application running on >>>>> Karaf. >>>>>>>>>>> >>>>>>>>>>> So, we have to think about "others projects" as well. >>>>>>>>>>> >>>>>>>>>>> I have no problem to upgrade to Spring 3.1.x but later (why not >>>>>>> imagine >>>>>>>>> a Karaf 2.4.x for that, it could be a good indicator), and propose >>>>> both >>>>>>>>> Spring 3.0 and 3.1 in Karaf 2.3.0 (depending of the impact, that I >>>>> gonna >>>>>>>>> test tonight). >>>>>>>>>> >>>>>>>>>> I agree with that.I know CXF has had very little testing with >>>>>>> Spring >>>>>>>>> 3.1.x.I would definitely prefer keeping on 3.0.7 for Karaf 2.3 >>>>> and >>>>>>>>> think about that for 2.4. >>>>>>>>>> >>>>>>>>>> I also agree that this is way to close to "release" to flip out a >>>>>>> major >>>>>>>>> component like spring. Maybe a month ago, but not now. >>>>>>>>> >>>>>>>>> Yeah I can understand the deadline issue as well. >>>>>>>>> >>>>>>>>> But its a shame that the new shiny Karaf 2.3.0 comes out of the box >>>>>>>>> with the old Spring 3.0.7 from Dec 2011. And there has not been any >>>>>>>>> new releases of Spring 3.0.x since. >>>>>>>>> >>>>>>>>> It would be cool if it was possible to provide an easy way for people >>>>>>>>> to switch Karaf to offer Spring 3.1. >>>>>>>>> Maybe that requires to offer a spring31 feature, and an easy way for >>>>>>>>> people to configure Karaf to use that. >>>>>>>>> >>>>>>>>> At Camel we have a CI job that tests Camel with Spring 3.1. The >>>>>>>>> upgrade for Camel has been painless. >>>>>>>>> >>>>>>>>> >>>>>>>>>> >>>>>>>>>> Dan >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> Regards >>>>>>>>>>> J
Re: Apache Karaf 2.3.0 very close
Jetty 8 should also be part of Karaf 2.x. On Tue, Oct 9, 2012 at 6:55 PM, Christian Schneider wrote: > I also would like to see Spring 3.1 in Karaf 2.4 and Jetty 8 in Karaf 3. > > If we need Spring 3.1 we can do an additional feature but I see no > imediate need for Karaf 2.3. > > Christian > > Am 09.10.2012 17:34, schrieb Achim Nierbeck: > > I second Dan on this only one point I'm not with you :) >> >> 2) don't do a 2.4 with jetty 8 but get Karaf 3.0 out of the door >> instead, we have Jetty 8 Support available there. >> >> regards, Achim >> >> 2012/10/9 Daniel Kulp : >> >>> On Oct 9, 2012, at 8:06 AM, Charles Moulliard wrote: >>> >>> Is it required to deliver Karaf 2.3.0 now or could we postpone it a few days till we provide Spring 3.1 ? >>> I don't think Spring 3.1 upgrade is a "few days" thing. And if you go >>> down that route, why don't we update to Jetty 8.1 which would bring in >>> Servlet 3 support (which CXF could leverage). Jetty 8 has been out for a >>> long time as well.And if we do that, we could update……… >>> >>> It's a never ending thing. At this point, we have been testing all the >>> various projects with Karaf 2.3 running with Spring 3.0.7, Jetty 7.6.x, >>> etc…. We know things are fairly stable with that. If we keep trying to >>> push things forward, we'll never get it out, or if we do, we won't have the >>> same level of testing and confidence. I know CXF has not been extensively >>> (or at all) tested with Spring 3.1. CXF uses spring a LOT more heavily >>> than Camel and we HAVE run into issues with the various Spring upgrades in >>> the past. I don't have a lot of confidence with it, and since CXF was >>> just released (artifacts promoted this morning), it would be several weeks >>> at least before we would normally get any fixes that may be needed for CXF >>> to work with Spring 3.1. From a CXF standpoint, I'm actually MORE >>> confident in a Jetty 8.1 upgrade than I am a Spring 3.1 upgrade as CXF does >>> test with Jetty 8.1 now. >>> >>> I would suggest: >>> >>> 1) Get 2.3 out ASAP using what we have been testing it with. It's WAY >>> WAY WAY overdue at this point. >>> >>> 2) Start a process of timed releases like CXF (and to a lesser extent >>> Camel). Timed releases avoid a lot of the feature creep. If it's there >>> in time, great. If not, there is always next release. 2.4 could just be >>> 3 months away with Sping 3.1 (or 3.2), Jetty 8.1, etc…Of course, get a >>> wiki page up that shows this roadmap so the other projects that use Karaf >>> heavily can plan accordingly and start testing. >>> >>> >>> >>> Dan >>> >>> >>> > -- > Christian Schneider > http://www.liquid-reality.de > > Open Source Architect > Talend Application Integration Division http://www.talend.com > > > -- Charles Moulliard Apache Committer / Sr. Enterprise Architect (RedHat) Twitter : @cmoulliard | Blog : http://cmoulliard.blogspot.com
Re: Apache Karaf 2.3.0 very close
I also would like to see Spring 3.1 in Karaf 2.4 and Jetty 8 in Karaf 3. If we need Spring 3.1 we can do an additional feature but I see no imediate need for Karaf 2.3. Christian Am 09.10.2012 17:34, schrieb Achim Nierbeck: I second Dan on this only one point I'm not with you :) 2) don't do a 2.4 with jetty 8 but get Karaf 3.0 out of the door instead, we have Jetty 8 Support available there. regards, Achim 2012/10/9 Daniel Kulp : On Oct 9, 2012, at 8:06 AM, Charles Moulliard wrote: Is it required to deliver Karaf 2.3.0 now or could we postpone it a few days till we provide Spring 3.1 ? I don't think Spring 3.1 upgrade is a "few days" thing. And if you go down that route, why don't we update to Jetty 8.1 which would bring in Servlet 3 support (which CXF could leverage). Jetty 8 has been out for a long time as well.And if we do that, we could update……… It's a never ending thing. At this point, we have been testing all the various projects with Karaf 2.3 running with Spring 3.0.7, Jetty 7.6.x, etc…. We know things are fairly stable with that. If we keep trying to push things forward, we'll never get it out, or if we do, we won't have the same level of testing and confidence. I know CXF has not been extensively (or at all) tested with Spring 3.1. CXF uses spring a LOT more heavily than Camel and we HAVE run into issues with the various Spring upgrades in the past. I don't have a lot of confidence with it, and since CXF was just released (artifacts promoted this morning), it would be several weeks at least before we would normally get any fixes that may be needed for CXF to work with Spring 3.1. From a CXF standpoint, I'm actually MORE confident in a Jetty 8.1 upgrade than I am a Spring 3.1 upgrade as CXF does test with Jetty 8.1 now. I would suggest: 1) Get 2.3 out ASAP using what we have been testing it with. It's WAY WAY WAY overdue at this point. 2) Start a process of timed releases like CXF (and to a lesser extent Camel). Timed releases avoid a lot of the feature creep. If it's there in time, great. If not, there is always next release. 2.4 could just be 3 months away with Sping 3.1 (or 3.2), Jetty 8.1, etc…Of course, get a wiki page up that shows this roadmap so the other projects that use Karaf heavily can plan accordingly and start testing. Dan -- Christian Schneider http://www.liquid-reality.de Open Source Architect Talend Application Integration Division http://www.talend.com
Re: Apache Karaf 2.3.0 very close
een >>>> any >>>>>>>>>> new releases of Spring 3.0.x since. >>>>>>>>>> >>>>>>>>>> It would be cool if it was possible to provide an easy way for >>>> people >>>>>>>>>> to switch Karaf to offer Spring 3.1. >>>>>>>>>> Maybe that requires to offer a spring31 feature, and an easy way >>>> for >>>>>>>>>> people to configure Karaf to use that. >>>>>>>>>> >>>>>>>>>> At Camel we have a CI job that tests Camel with Spring 3.1. The >>>>>>>>>> upgrade for Camel has been painless. >>>>>>>>>> >>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> Dan >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> Regards >>>>>>>>>>>> JB >>>>>>>>>>>> >>>>>>>>>>>> On 10/08/2012 06:48 PM, Claus Ibsen wrote: >>>>>>>>>>>>> On Mon, Oct 8, 2012 at 6:44 PM, Jean-Baptiste Onofré < >>>>>>>> j...@nanthrax.net> >>>>>>>>>> wrote: >>>>>>>>>>>>>> Camel 2.10.x uses Spring 3.0.7 for now, for we are "aligned" >>>>>> with >>>>>>>>>> Camel >>>>>>>>>>>>>> 2.10. >>>>>>>>>>>>>> >>>>>>>>>>>>>> Does it make sense to update to Spring 3.1.x (for future >>>> Camel >>>>>>>> version >>>>>>>>>>>>>> maybe) ? >>>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> Well Camel 2.10 supports both Spring 3.0.x and 3.1.x. And we >>>> are >>>>>>>>>>>>> frankly only holding back because of Karaf. >>>>>>>>>>>>> As when people deploy Camel in Karaf they inherit the spring >>>> from >>>>>>>>>> Karaf. >>>>>>>>>>>>> >>>>>>>>>>>>> People in the community would like to use Spring 3.1.x as its >>>>>> been >>>>>>>> out >>>>>>>>>>>>> since December 2011. >>>>>>>>>>>>> And its the stable release path where they cut new releases. >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> Regards >>>>>>>>>>>>>> JB >>>>>>>>>>>>>> >>>>>>>>>>>>>> On 10/08/2012 05:55 PM, Claus Ibsen wrote: >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> On Mon, Oct 8, 2012 at 5:45 PM, Jamie G. < >>>>>>>> jamie.goody...@gmail.com> >>>>>>>>>> wrote: >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> Hi Claus, >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> From the Karaf 2.3.0 pom file: >>>>>>>>>>>>>>>> 1.2.1 >>>>>>>>>>>>>>>> 2.5.6.SEC03 >>>>>>>>>>>>>>>> 3.0.7.RELEASE >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> Crap I think you guys shoulder consider switching to the >>>> 3.1.2 >>>>>>>>>> release >>>>>>>>>>>>>>> of Spring. >>>>>>>>>>>>>>> As well Jetty 7.6.7, so people have the latest stable >>>> release >>>>>> of >>>>>>>>>> these >>>>>>>>>>>>>>> 2 important pieces. >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> Cheers, >>>>>>>>>>>>>>>> Jamie >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> On Mon, Oct 8, 2012 at 1:09 PM, Claus Ibsen < >>>>>>>> claus.ib...@gmail.com> >>>>>>>>>>>>>>>> wrote: >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> Hi >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> What Spring version does Karaf 2.3.0 come with out of the >>>>>> box? >>>>>>>>>> 3.0.x >>>>>>>>>>>>>>>>> or the newer 3.1.x ? >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> On Mon, Oct 8, 2012 at 10:53 AM, Jamie G. < >>>>>>>>>> jamie.goody...@gmail.com> >>>>>>>>>>>>>>>>> wrote: >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> I'm always ready! >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> Cheers, >>>>>>>>>>>>>>>>>> Jamie >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> On Mon, Oct 8, 2012 at 5:08 AM, j...@nanthrax.net < >>>>>>>> j...@nanthrax.net> >>>>>>>>>>>>>>>>>> wrote: >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> Great, thanks a lot ! >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> -- >>>>>>>>>>>>>>>>>>> Jean-Baptiste Onofré >>>>>>>>>>>>>>>>>>> jbono...@apache.org >>>>>>>>>>>>>>>>>>> http://blog.nanthrax.net >>>>>>>>>>>>>>>>>>> Talend - http://wwx.talend.com >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> - Reply message - >>>>>>>>>>>>>>>>>>> From: "Andreas Pieber" >>>>>>>>>>>>>>>>>>> To: >>>>>>>>>>>>>>>>>>> Subject: Apache Karaf 2.3.0 very close >>>>>>>>>>>>>>>>>>> Date: Mon, Oct 8, 2012 9:17 am >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> Hey, >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> On Mon, Oct 8, 2012 at 7:46 AM, Jean-Baptiste Onofré < >>>>>>>>>> j...@nanthrax.net> >>>>>>>>>>>>>>>>>>> wrote: >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> @Andreas, could you take a look on KARAF-1878 and >>>>>> KARAF-1752 >>>>>>>>>>>>>>>>>>>> (assigned to >>>>>>>>>>>>>>>>>>>> you) ? If you are busy today, I think we can postpone >>>> to >>>>>>>> 2.3.1. >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> I wanted to keep KARAF-1878 opened for review till >>>> tonight; >>>>>>>> I'll >>>>>>>>>> apply >>>>>>>>>>>>>>>>>>> afterwards. I'll also apply KARAF-1752 then. >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> Kind regards, >>>>>>>>>>>>>>>>>>> Andreas >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> Thanks all guys, >>>>>>>>>>>>>>>>>>>> Regards >>>>>>>>>>>>>>>>>>>> JB >>>>>>>>>>>>>>>>>>>> -- >>>>>>>>>>>>>>>>>>>> Jean-Baptiste Onofré >>>>>>>>>>>>>>>>>>>> jbono...@apache.org >>>>>>>>>>>>>>>>>>>> http://blog.nanthrax.net >>>>>>>>>>>>>>>>>>>> Talend - http://www.talend.com >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> -- >>>>>>>>>>>>>>>>> Claus Ibsen >>>>>>>>>>>>>>>>> - >>>>>>>>>>>>>>>>> Red Hat, Inc. >>>>>>>>>>>>>>>>> FuseSource is now part of Red Hat >>>>>>>>>>>>>>>>> Email: cib...@redhat.com >>>>>>>>>>>>>>>>> Web: http://fusesource.com >>>>>>>>>>>>>>>>> Twitter: davsclaus >>>>>>>>>>>>>>>>> Blog: http://davsclaus.com >>>>>>>>>>>>>>>>> Author of Camel in Action: http://www.manning.com/ibsen >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> -- >>>>>>>>>>>>>> Jean-Baptiste Onofré >>>>>>>>>>>>>> jbono...@apache.org >>>>>>>>>>>>>> http://blog.nanthrax.net >>>>>>>>>>>>>> Talend - http://www.talend.com >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> -- >>>>>>>>>>>> Jean-Baptiste Onofré >>>>>>>>>>>> jbono...@apache.org >>>>>>>>>>>> http://blog.nanthrax.net >>>>>>>>>>>> Talend - http://www.talend.com >>>>>>>>>>> >>>>>>>>>>> -- >>>>>>>>>>> Daniel Kulp >>>>>>>>>>> dk...@apache.org - http://dankulp.com/blog >>>>>>>>>>> Talend Community Coder - http://coders.talend.com >>>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> -- >>>>>>>>>> Claus Ibsen >>>>>>>>>> - >>>>>>>>>> Red Hat, Inc. >>>>>>>>>> FuseSource is now part of Red Hat >>>>>>>>>> Email: cib...@redhat.com >>>>>>>>>> Web: http://fusesource.com >>>>>>>>>> Twitter: davsclaus >>>>>>>>>> Blog: http://davsclaus.com >>>>>>>>>> Author of Camel in Action: http://www.manning.com/ibsen >>>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> -- >>>>>>>>> Charles Moulliard >>>>>>>>> Apache Committer / Sr. Enterprise Architect (RedHat) >>>>>>>>> Twitter : @cmoulliard | Blog : http://cmoulliard.blogspot.com >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> -- >>>>>>>> >>>>>>>> Apache Karaf <http://karaf.apache.org/> Committer & PMC >>>>>>>> OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/> >>>>>>>> Committer & Project Lead >>>>>>>> OPS4J Pax for Vaadin >>>>>>>> <http://team.ops4j.org/wiki/display/PAXVAADIN/Home> Commiter & >>>> Project >>>>>>>> Lead >>>>>>>> blog <http://notizblog.nierbeck.de/> >>>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> >>>>>>> Guillaume Nodet >>>>>>> >>>>>>> Blog: http://gnodet.blogspot.com/ >>>>>>> >>>>>>> FuseSource, Integration everywhere >>>>>>> http://fusesource.com >>>>>> >>>>> >>>>> >>>>> >>>>> -- >>>> >>> >>> >>> >>> -- >>> Charles Moulliard >>> Apache Committer / Sr. Enterprise Architect (RedHat) >>> Twitter : @cmoulliard | Blog : http://cmoulliard.blogspot.com >> >> -- >> Daniel Kulp >> dk...@apache.org - http://dankulp.com/blog >> Talend Community Coder - http://coders.talend.com >> > > > > -- > > Apache Karaf <http://karaf.apache.org/> Committer & PMC > OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/> > Committer & Project Lead > OPS4J Pax for Vaadin > <http://team.ops4j.org/wiki/display/PAXVAADIN/Home> Commiter & Project > Lead > blog <http://notizblog.nierbeck.de/> -- Daniel Kulp dk...@apache.org - http://dankulp.com/blog Talend Community Coder - http://coders.talend.com
Re: Apache Karaf 2.3.0 very close
t;>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> Regards >>>>>>>>>>> JB >>>>>>>>>>> >>>>>>>>>>> On 10/08/2012 06:48 PM, Claus Ibsen wrote: >>>>>>>>>>>> On Mon, Oct 8, 2012 at 6:44 PM, Jean-Baptiste Onofré < >>>>>>> j...@nanthrax.net> >>>>>>>>> wrote: >>>>>>>>>>>>> Camel 2.10.x uses Spring 3.0.7 for now, for we are "aligned" >>>>> with >>>>>>>>> Camel >>>>>>>>>>>>> 2.10. >>>>>>>>>>>>> >>>>>>>>>>>>> Does it make sense to update to Spring 3.1.x (for future >>> Camel >>>>>>> version >>>>>>>>>>>>> maybe) ? >>>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> Well Camel 2.10 supports both Spring 3.0.x and 3.1.x. And we >>> are >>>>>>>>>>>> frankly only holding back because of Karaf. >>>>>>>>>>>> As when people deploy Camel in Karaf they inherit the spring >>> from >>>>>>>>> Karaf. >>>>>>>>>>>> >>>>>>>>>>>> People in the community would like to use Spring 3.1.x as its >>>>> been >>>>>>> out >>>>>>>>>>>> since December 2011. >>>>>>>>>>>> And its the stable release path where they cut new releases. >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> Regards >>>>>>>>>>>>> JB >>>>>>>>>>>>> >>>>>>>>>>>>> On 10/08/2012 05:55 PM, Claus Ibsen wrote: >>>>>>>>>>>>>> >>>>>>>>>>>>>> On Mon, Oct 8, 2012 at 5:45 PM, Jamie G. < >>>>>>> jamie.goody...@gmail.com> >>>>>>>>> wrote: >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> Hi Claus, >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> From the Karaf 2.3.0 pom file: >>>>>>>>>>>>>>> 1.2.1 >>>>>>>>>>>>>>> 2.5.6.SEC03 >>>>>>>>>>>>>>> 3.0.7.RELEASE >>>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> Crap I think you guys shoulder consider switching to the >>> 3.1.2 >>>>>>>>> release >>>>>>>>>>>>>> of Spring. >>>>>>>>>>>>>> As well Jetty 7.6.7, so people have the latest stable >>> release >>>>> of >>>>>>>>> these >>>>>>>>>>>>>> 2 important pieces. >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>>> Cheers, >>>>>>>>>>>>>>> Jamie >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> On Mon, Oct 8, 2012 at 1:09 PM, Claus Ibsen < >>>>>>> claus.ib...@gmail.com> >>>>>>>>>>>>>>> wrote: >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> Hi >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> What Spring version does Karaf 2.3.0 come with out of the >>>>> box? >>>>>>>>> 3.0.x >>>>>>>>>>>>>>>> or the newer 3.1.x ? >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> On Mon, Oct 8, 2012 at 10:53 AM, Jamie G. < >>>>>>>>> jamie.goody...@gmail.com> >>>>>>>>>>>>>>>> wrote: >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> I'm always ready! >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> Cheers, >>>>>>>>>>>>>>>>> Jamie >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> On Mon, Oct 8, 2012 at 5:08 AM, j...@nanthrax.net < >>>>>>> j...@nanthrax.net> >>>>>>>>>>>>>>>>> wrote: >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> Great, thanks a lot ! >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> -- >>>>>>>>>>>>>>>>>> Jean-Baptiste Onofré >>>>>>>>>>>>>>>>>> jbono...@apache.org >>>>>>>>>>>>>>>>>> http://blog.nanthrax.net >>>>>>>>>>>>>>>>>> Talend - http://wwx.talend.com >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> - Reply message - >>>>>>>>>>>>>>>>>> From: "Andreas Pieber" >>>>>>>>>>>>>>>>>> To: >>>>>>>>>>>>>>>>>> Subject: Apache Karaf 2.3.0 very close >>>>>>>>>>>>>>>>>> Date: Mon, Oct 8, 2012 9:17 am >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> Hey, >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> On Mon, Oct 8, 2012 at 7:46 AM, Jean-Baptiste Onofré < >>>>>>>>> j...@nanthrax.net> >>>>>>>>>>>>>>>>>> wrote: >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> @Andreas, could you take a look on KARAF-1878 and >>>>> KARAF-1752 >>>>>>>>>>>>>>>>>>> (assigned to >>>>>>>>>>>>>>>>>>> you) ? If you are busy today, I think we can postpone >>> to >>>>>>> 2.3.1. >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> I wanted to keep KARAF-1878 opened for review till >>> tonight; >>>>>>> I'll >>>>>>>>> apply >>>>>>>>>>>>>>>>>> afterwards. I'll also apply KARAF-1752 then. >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> Kind regards, >>>>>>>>>>>>>>>>>> Andreas >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> Thanks all guys, >>>>>>>>>>>>>>>>>>> Regards >>>>>>>>>>>>>>>>>>> JB >>>>>>>>>>>>>>>>>>> -- >>>>>>>>>>>>>>>>>>> Jean-Baptiste Onofré >>>>>>>>>>>>>>>>>>> jbono...@apache.org >>>>>>>>>>>>>>>>>>> http://blog.nanthrax.net >>>>>>>>>>>>>>>>>>> Talend - http://www.talend.com >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> -- >>>>>>>>>>>>>>>> Claus Ibsen >>>>>>>>>>>>>>>> - >>>>>>>>>>>>>>>> Red Hat, Inc. >>>>>>>>>>>>>>>> FuseSource is now part of Red Hat >>>>>>>>>>>>>>>> Email: cib...@redhat.com >>>>>>>>>>>>>>>> Web: http://fusesource.com >>>>>>>>>>>>>>>> Twitter: davsclaus >>>>>>>>>>>>>>>> Blog: http://davsclaus.com >>>>>>>>>>>>>>>> Author of Camel in Action: http://www.manning.com/ibsen >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> -- >>>>>>>>>>>>> Jean-Baptiste Onofré >>>>>>>>>>>>> jbono...@apache.org >>>>>>>>>>>>> http://blog.nanthrax.net >>>>>>>>>>>>> Talend - http://www.talend.com >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> -- >>>>>>>>>>> Jean-Baptiste Onofré >>>>>>>>>>> jbono...@apache.org >>>>>>>>>>> http://blog.nanthrax.net >>>>>>>>>>> Talend - http://www.talend.com >>>>>>>>>> >>>>>>>>>> -- >>>>>>>>>> Daniel Kulp >>>>>>>>>> dk...@apache.org - http://dankulp.com/blog >>>>>>>>>> Talend Community Coder - http://coders.talend.com >>>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> -- >>>>>>>>> Claus Ibsen >>>>>>>>> - >>>>>>>>> Red Hat, Inc. >>>>>>>>> FuseSource is now part of Red Hat >>>>>>>>> Email: cib...@redhat.com >>>>>>>>> Web: http://fusesource.com >>>>>>>>> Twitter: davsclaus >>>>>>>>> Blog: http://davsclaus.com >>>>>>>>> Author of Camel in Action: http://www.manning.com/ibsen >>>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> -- >>>>>>>> Charles Moulliard >>>>>>>> Apache Committer / Sr. Enterprise Architect (RedHat) >>>>>>>> Twitter : @cmoulliard | Blog : http://cmoulliard.blogspot.com >>>>>>> >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> >>>>>>> Apache Karaf <http://karaf.apache.org/> Committer & PMC >>>>>>> OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/> >>>>>>> Committer & Project Lead >>>>>>> OPS4J Pax for Vaadin >>>>>>> <http://team.ops4j.org/wiki/display/PAXVAADIN/Home> Commiter & >>> Project >>>>>>> Lead >>>>>>> blog <http://notizblog.nierbeck.de/> >>>>>>> >>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> >>>>>> Guillaume Nodet >>>>>> >>>>>> Blog: http://gnodet.blogspot.com/ >>>>>> >>>>>> FuseSource, Integration everywhere >>>>>> http://fusesource.com >>>>> >>>> >>>> >>>> >>>> -- >>> >> >> >> >> -- >> Charles Moulliard >> Apache Committer / Sr. Enterprise Architect (RedHat) >> Twitter : @cmoulliard | Blog : http://cmoulliard.blogspot.com > > -- > Daniel Kulp > dk...@apache.org - http://dankulp.com/blog > Talend Community Coder - http://coders.talend.com > -- Apache Karaf <http://karaf.apache.org/> Committer & PMC OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/> Committer & Project Lead OPS4J Pax for Vaadin <http://team.ops4j.org/wiki/display/PAXVAADIN/Home> Commiter & Project Lead blog <http://notizblog.nierbeck.de/>
Re: Apache Karaf 2.3.0 very close
aus's >>>>>>> remark to also have Spring 3.1 for Camel and others projects. >>>>>>> >>>>>>> What I would like to propose is that we create for Karaf/ServiceMix >>>>>>> projects a page containing a table of the different software used >> and >>>>>> have >>>>>>> a roadmap about them. This question is important not only for >> Spring >>>>>>> framework but also Pax, Aries, Felix, ... which are (re)packaged >> into >>>>>>> Karaf/ServiceMix >>>>>>> This will avoid that we discover a few days before the publication >> of >>>> a >>>>>>> release that we have miss something >>>>>>> >>>>>>> Just my 5€ cents. >>>>>>> >>>>>>> On Tue, Oct 9, 2012 at 8:19 AM, Claus Ibsen >> >>>>>> wrote: >>>>>>> >>>>>>>> On Mon, Oct 8, 2012 at 7:30 PM, Daniel Kulp >>>> wrote: >>>>>>>>> >>>>>>>>> On Oct 8, 2012, at 1:08 PM, Jean-Baptiste Onofré < >> j...@nanthrax.net> >>>>>>>> wrote: >>>>>>>>> >>>>>>>>>> Agree Claus, but Camel is not the only application running on >>>> Karaf. >>>>>>>>>> >>>>>>>>>> So, we have to think about "others projects" as well. >>>>>>>>>> >>>>>>>>>> I have no problem to upgrade to Spring 3.1.x but later (why not >>>>>> imagine >>>>>>>> a Karaf 2.4.x for that, it could be a good indicator), and propose >>>> both >>>>>>>> Spring 3.0 and 3.1 in Karaf 2.3.0 (depending of the impact, that I >>>> gonna >>>>>>>> test tonight). >>>>>>>>> >>>>>>>>> I agree with that.I know CXF has had very little testing >> with >>>>>> Spring >>>>>>>> 3.1.x.I would definitely prefer keeping on 3.0.7 for Karaf 2.3 >>>> and >>>>>>>> think about that for 2.4. >>>>>>>>> >>>>>>>>> I also agree that this is way to close to "release" to flip out >> a >>>>>> major >>>>>>>> component like spring. Maybe a month ago, but not now. >>>>>>>>> >>>>>>>> >>>>>>>> Yeah I can understand the deadline issue as well. >>>>>>>> >>>>>>>> But its a shame that the new shiny Karaf 2.3.0 comes out of the >> box >>>>>>>> with the old Spring 3.0.7 from Dec 2011. And there has not been >> any >>>>>>>> new releases of Spring 3.0.x since. >>>>>>>> >>>>>>>> It would be cool if it was possible to provide an easy way for >> people >>>>>>>> to switch Karaf to offer Spring 3.1. >>>>>>>> Maybe that requires to offer a spring31 feature, and an easy way >> for >>>>>>>> people to configure Karaf to use that. >>>>>>>> >>>>>>>> At Camel we have a CI job that tests Camel with Spring 3.1. The >>>>>>>> upgrade for Camel has been painless. >>>>>>>> >>>>>>>> >>>>>>>>> >>>>>>>>> Dan >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>>> >>>>>>>>>> Regards >>>>>>>>>> JB >>>>>>>>>> >>>>>>>>>> On 10/08/2012 06:48 PM, Claus Ibsen wrote: >>>>>>>>>>> On Mon, Oct 8, 2012 at 6:44 PM, Jean-Baptiste Onofré < >>>>>> j...@nanthrax.net> >>>>>>>> wrote: >>>>>>>>>>>> Camel 2.10.x uses Spring 3.0.7 for now, for we are "aligned" >>>> with >>>>>>>> Camel >>>>>>>>>>>> 2.10. >>>>>>>>>>>> >>>>>>>>>>>> Does it make sense to update to Spring 3.1.x (for
Re: Apache Karaf 2.3.0 very close
ee about >>>> Claus's >>>>>>> remark to also have Spring 3.1 for Camel and others projects. >>>>>>> >>>>>>> What I would like to propose is that we create for Karaf/ServiceMix >>>>>>> projects a page containing a table of the different software used and >>>>>> have >>>>>>> a roadmap about them. This question is important not only for Spring >>>>>>> framework but also Pax, Aries, Felix, ... which are (re)packaged into >>>>>>> Karaf/ServiceMix >>>>>>> This will avoid that we discover a few days before the publication of >>>> a >>>>>>> release that we have miss something >>>>>>> >>>>>>> Just my 5€ cents. >>>>>>> >>>>>>> On Tue, Oct 9, 2012 at 8:19 AM, Claus Ibsen >>>>>> wrote: >>>>>>> >>>>>>>> On Mon, Oct 8, 2012 at 7:30 PM, Daniel Kulp >>>> wrote: >>>>>>>>> >>>>>>>>> On Oct 8, 2012, at 1:08 PM, Jean-Baptiste Onofré >>>>>>>> wrote: >>>>>>>>> >>>>>>>>>> Agree Claus, but Camel is not the only application running on >>>> Karaf. >>>>>>>>>> >>>>>>>>>> So, we have to think about "others projects" as well. >>>>>>>>>> >>>>>>>>>> I have no problem to upgrade to Spring 3.1.x but later (why not >>>>>> imagine >>>>>>>> a Karaf 2.4.x for that, it could be a good indicator), and propose >>>> both >>>>>>>> Spring 3.0 and 3.1 in Karaf 2.3.0 (depending of the impact, that I >>>> gonna >>>>>>>> test tonight). >>>>>>>>> >>>>>>>>> I agree with that.I know CXF has had very little testing with >>>>>> Spring >>>>>>>> 3.1.x.I would definitely prefer keeping on 3.0.7 for Karaf 2.3 >>>> and >>>>>>>> think about that for 2.4. >>>>>>>>> >>>>>>>>> I also agree that this is way to close to "release" to flip out a >>>>>> major >>>>>>>> component like spring. Maybe a month ago, but not now. >>>>>>>> >>>>>>>> Yeah I can understand the deadline issue as well. >>>>>>>> >>>>>>>> But its a shame that the new shiny Karaf 2.3.0 comes out of the box >>>>>>>> with the old Spring 3.0.7 from Dec 2011. And there has not been any >>>>>>>> new releases of Spring 3.0.x since. >>>>>>>> >>>>>>>> It would be cool if it was possible to provide an easy way for people >>>>>>>> to switch Karaf to offer Spring 3.1. >>>>>>>> Maybe that requires to offer a spring31 feature, and an easy way for >>>>>>>> people to configure Karaf to use that. >>>>>>>> >>>>>>>> At Camel we have a CI job that tests Camel with Spring 3.1. The >>>>>>>> upgrade for Camel has been painless. >>>>>>>> >>>>>>>> >>>>>>>>> >>>>>>>>> Dan >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>>> >>>>>>>>>> Regards >>>>>>>>>> JB >>>>>>>>>> >>>>>>>>>> On 10/08/2012 06:48 PM, Claus Ibsen wrote: >>>>>>>>>>> On Mon, Oct 8, 2012 at 6:44 PM, Jean-Baptiste Onofré < >>>>>> j...@nanthrax.net> >>>>>>>> wrote: >>>>>>>>>>>> Camel 2.10.x uses Spring 3.0.7 for now, for we are "aligned" >>>> with >>>>>>>> Camel >>>>>>>>>>>> 2.10. >>>>>>>>>>>> >>>>>>>>>>>> Does it make sense to update to Spring 3.1.x (for future Camel >>>>>> version >>>>>>>>>>>> maybe) ? >>>>>>&g
Re: Apache Karaf 2.3.0 very close
gt;>> >> >> On Mon, Oct 8, 2012 at 7:30 PM, Daniel Kulp >>> wrote: >>> >> >> > >>> >> >> > On Oct 8, 2012, at 1:08 PM, Jean-Baptiste Onofré >>> >> >> wrote: >>> >> >> > >>> >> >> >> Agree Claus, but Camel is not the only application running on >>> Karaf. >>> >> >> >> >>> >> >> >> So, we have to think about "others projects" as well. >>> >> >> >> >>> >> >> >> I have no problem to upgrade to Spring 3.1.x but later (why not >>> >> imagine >>> >> >> a Karaf 2.4.x for that, it could be a good indicator), and propose >>> both >>> >> >> Spring 3.0 and 3.1 in Karaf 2.3.0 (depending of the impact, that I >>> gonna >>> >> >> test tonight). >>> >> >> > >>> >> >> > I agree with that.I know CXF has had very little testing with >>> >> Spring >>> >> >> 3.1.x.I would definitely prefer keeping on 3.0.7 for Karaf 2.3 >>> and >>> >> >> think about that for 2.4. >>> >> >> > >>> >> >> > I also agree that this is way to close to "release" to flip out a >>> >> major >>> >> >> component like spring. Maybe a month ago, but not now. >>> >> >> > >>> >> >> >>> >> >> Yeah I can understand the deadline issue as well. >>> >> >> >>> >> >> But its a shame that the new shiny Karaf 2.3.0 comes out of the box >>> >> >> with the old Spring 3.0.7 from Dec 2011. And there has not been any >>> >> >> new releases of Spring 3.0.x since. >>> >> >> >>> >> >> It would be cool if it was possible to provide an easy way for people >>> >> >> to switch Karaf to offer Spring 3.1. >>> >> >> Maybe that requires to offer a spring31 feature, and an easy way for >>> >> >> people to configure Karaf to use that. >>> >> >> >>> >> >> At Camel we have a CI job that tests Camel with Spring 3.1. The >>> >> >> upgrade for Camel has been painless. >>> >> >> >>> >> >> >>> >> >> > >>> >> >> > Dan >>> >> >> > >>> >> >> > >>> >> >> > >>> >> >> > >>> >> >> >> >>> >> >> >> Regards >>> >> >> >> JB >>> >> >> >> >>> >> >> >> On 10/08/2012 06:48 PM, Claus Ibsen wrote: >>> >> >> >>> On Mon, Oct 8, 2012 at 6:44 PM, Jean-Baptiste Onofré < >>> >> j...@nanthrax.net> >>> >> >> wrote: >>> >> >> >>>> Camel 2.10.x uses Spring 3.0.7 for now, for we are "aligned" >>> with >>> >> >> Camel >>> >> >> >>>> 2.10. >>> >> >> >>>> >>> >> >> >>>> Does it make sense to update to Spring 3.1.x (for future Camel >>> >> version >>> >> >> >>>> maybe) ? >>> >> >> >>>> >>> >> >> >>> >>> >> >> >>> Well Camel 2.10 supports both Spring 3.0.x and 3.1.x. And we are >>> >> >> >>> frankly only holding back because of Karaf. >>> >> >> >>> As when people deploy Camel in Karaf they inherit the spring from >>> >> >> Karaf. >>> >> >> >>> >>> >> >> >>> People in the community would like to use Spring 3.1.x as its >>> been >>> >> out >>> >> >> >>> since December 2011. >>> >> >> >>> And its the stable release path where they cut new releases. >>> >> >> >>> >>> >> >> >>> >>> >> >> >>>> >>> >> >> >>>> Regards >>> >> >> >>>> JB >>> >> >> >>>> >>> >> >> >>>> On 10/08/2012 05:55 PM, Claus Ibsen wrote: &g
Re: Apache Karaf 2.3.0 very close
>> >> >> > > >> >> >> > I agree with that.I know CXF has had very little testing > with > >> >> Spring > >> >> >> 3.1.x.I would definitely prefer keeping on 3.0.7 for Karaf 2.3 > >> and > >> >> >> think about that for 2.4. > >> >> >> > > >> >> >> > I also agree that this is way to close to "release" to flip out > a > >> >> major > >> >> >> component like spring. Maybe a month ago, but not now. > >> >> >> > > >> >> >> > >> >> >> Yeah I can understand the deadline issue as well. > >> >> >> > >> >> >> But its a shame that the new shiny Karaf 2.3.0 comes out of the > box > >> >> >> with the old Spring 3.0.7 from Dec 2011. And there has not been > any > >> >> >> new releases of Spring 3.0.x since. > >> >> >> > >> >> >> It would be cool if it was possible to provide an easy way for > people > >> >> >> to switch Karaf to offer Spring 3.1. > >> >> >> Maybe that requires to offer a spring31 feature, and an easy way > for > >> >> >> people to configure Karaf to use that. > >> >> >> > >> >> >> At Camel we have a CI job that tests Camel with Spring 3.1. The > >> >> >> upgrade for Camel has been painless. > >> >> >> > >> >> >> > >> >> >> > > >> >> >> > Dan > >> >> >> > > >> >> >> > > >> >> >> > > >> >> >> > > >> >> >> >> > >> >> >> >> Regards > >> >> >> >> JB > >> >> >> >> > >> >> >> >> On 10/08/2012 06:48 PM, Claus Ibsen wrote: > >> >> >> >>> On Mon, Oct 8, 2012 at 6:44 PM, Jean-Baptiste Onofré < > >> >> j...@nanthrax.net> > >> >> >> wrote: > >> >> >> >>>> Camel 2.10.x uses Spring 3.0.7 for now, for we are "aligned" > >> with > >> >> >> Camel > >> >> >> >>>> 2.10. > >> >> >> >>>> > >> >> >> >>>> Does it make sense to update to Spring 3.1.x (for future > Camel > >> >> version > >> >> >> >>>> maybe) ? > >> >> >> >>>> > >> >> >> >>> > >> >> >> >>> Well Camel 2.10 supports both Spring 3.0.x and 3.1.x. And we > are > >> >> >> >>> frankly only holding back because of Karaf. > >> >> >> >>> As when people deploy Camel in Karaf they inherit the spring > from > >> >> >> Karaf. > >> >> >> >>> > >> >> >> >>> People in the community would like to use Spring 3.1.x as its > >> been > >> >> out > >> >> >> >>> since December 2011. > >> >> >> >>> And its the stable release path where they cut new releases. > >> >> >> >>> > >> >> >> >>> > >> >> >> >>>> > >> >> >> >>>> Regards > >> >> >> >>>> JB > >> >> >> >>>> > >> >> >> >>>> On 10/08/2012 05:55 PM, Claus Ibsen wrote: > >> >> >> >>>>> > >> >> >> >>>>> On Mon, Oct 8, 2012 at 5:45 PM, Jamie G. < > >> >> jamie.goody...@gmail.com> > >> >> >> wrote: > >> >> >> >>>>>> > >> >> >> >>>>>> Hi Claus, > >> >> >> >>>>>> > >> >> >> >>>>>> From the Karaf 2.3.0 pom file: > >> >> >> >>>>>> 1.2.1 > >> >> >> >>>>>> 2.5.6.SEC03 > >> >> >> >>>>>> 3.0.7.RELEASE > >> >> >> >>>>>> > >> >> >> >>>>> > >> >> >> >>>>> Crap I think you guys shoulder c
Re: Apache Karaf 2.3.0 very close
its a shame that the new shiny Karaf 2.3.0 comes out of the box >> >> >> with the old Spring 3.0.7 from Dec 2011. And there has not been any >> >> >> new releases of Spring 3.0.x since. >> >> >> >> >> >> It would be cool if it was possible to provide an easy way for people >> >> >> to switch Karaf to offer Spring 3.1. >> >> >> Maybe that requires to offer a spring31 feature, and an easy way for >> >> >> people to configure Karaf to use that. >> >> >> >> >> >> At Camel we have a CI job that tests Camel with Spring 3.1. The >> >> >> upgrade for Camel has been painless. >> >> >> >> >> >> >> >> >> > >> >> >> > Dan >> >> >> > >> >> >> > >> >> >> > >> >> >> > >> >> >> >> >> >> >> >> Regards >> >> >> >> JB >> >> >> >> >> >> >> >> On 10/08/2012 06:48 PM, Claus Ibsen wrote: >> >> >> >>> On Mon, Oct 8, 2012 at 6:44 PM, Jean-Baptiste Onofré < >> >> j...@nanthrax.net> >> >> >> wrote: >> >> >> >>>> Camel 2.10.x uses Spring 3.0.7 for now, for we are "aligned" >> with >> >> >> Camel >> >> >> >>>> 2.10. >> >> >> >>>> >> >> >> >>>> Does it make sense to update to Spring 3.1.x (for future Camel >> >> version >> >> >> >>>> maybe) ? >> >> >> >>>> >> >> >> >>> >> >> >> >>> Well Camel 2.10 supports both Spring 3.0.x and 3.1.x. And we are >> >> >> >>> frankly only holding back because of Karaf. >> >> >> >>> As when people deploy Camel in Karaf they inherit the spring from >> >> >> Karaf. >> >> >> >>> >> >> >> >>> People in the community would like to use Spring 3.1.x as its >> been >> >> out >> >> >> >>> since December 2011. >> >> >> >>> And its the stable release path where they cut new releases. >> >> >> >>> >> >> >> >>> >> >> >> >>>> >> >> >> >>>> Regards >> >> >> >>>> JB >> >> >> >>>> >> >> >> >>>> On 10/08/2012 05:55 PM, Claus Ibsen wrote: >> >> >> >>>>> >> >> >> >>>>> On Mon, Oct 8, 2012 at 5:45 PM, Jamie G. < >> >> jamie.goody...@gmail.com> >> >> >> wrote: >> >> >> >>>>>> >> >> >> >>>>>> Hi Claus, >> >> >> >>>>>> >> >> >> >>>>>> From the Karaf 2.3.0 pom file: >> >> >> >>>>>> 1.2.1 >> >> >> >>>>>> 2.5.6.SEC03 >> >> >> >>>>>> 3.0.7.RELEASE >> >> >> >>>>>> >> >> >> >>>>> >> >> >> >>>>> Crap I think you guys shoulder consider switching to the 3.1.2 >> >> >> release >> >> >> >>>>> of Spring. >> >> >> >>>>> As well Jetty 7.6.7, so people have the latest stable release >> of >> >> >> these >> >> >> >>>>> 2 important pieces. >> >> >> >>>>> >> >> >> >>>>> >> >> >> >>>>> >> >> >> >>>>> >> >> >> >>>>>> Cheers, >> >> >> >>>>>> Jamie >> >> >> >>>>>> >> >> >> >>>>>> On Mon, Oct 8, 2012 at 1:09 PM, Claus Ibsen < >> >> claus.ib...@gmail.com> >> >> >> >>>>>> wrote: >> >> >> >>>>>>> >> >> >> >>>>>>> Hi >> >> >> >>>>>>> >> >> >> >>>>>>> What Spring version
Re: Apache Karaf 2.3.0 very close
>> >> > > >> >> > Dan > >> >> > > >> >> > > >> >> > > >> >> > > >> >> >> > >> >> >> Regards > >> >> >> JB > >> >> >> > >> >> >> On 10/08/2012 06:48 PM, Claus Ibsen wrote: > >> >> >>> On Mon, Oct 8, 2012 at 6:44 PM, Jean-Baptiste Onofré < > >> j...@nanthrax.net> > >> >> wrote: > >> >> >>>> Camel 2.10.x uses Spring 3.0.7 for now, for we are "aligned" > with > >> >> Camel > >> >> >>>> 2.10. > >> >> >>>> > >> >> >>>> Does it make sense to update to Spring 3.1.x (for future Camel > >> version > >> >> >>>> maybe) ? > >> >> >>>> > >> >> >>> > >> >> >>> Well Camel 2.10 supports both Spring 3.0.x and 3.1.x. And we are > >> >> >>> frankly only holding back because of Karaf. > >> >> >>> As when people deploy Camel in Karaf they inherit the spring from > >> >> Karaf. > >> >> >>> > >> >> >>> People in the community would like to use Spring 3.1.x as its > been > >> out > >> >> >>> since December 2011. > >> >> >>> And its the stable release path where they cut new releases. > >> >> >>> > >> >> >>> > >> >> >>>> > >> >> >>>> Regards > >> >> >>>> JB > >> >> >>>> > >> >> >>>> On 10/08/2012 05:55 PM, Claus Ibsen wrote: > >> >> >>>>> > >> >> >>>>> On Mon, Oct 8, 2012 at 5:45 PM, Jamie G. < > >> jamie.goody...@gmail.com> > >> >> wrote: > >> >> >>>>>> > >> >> >>>>>> Hi Claus, > >> >> >>>>>> > >> >> >>>>>> From the Karaf 2.3.0 pom file: > >> >> >>>>>> 1.2.1 > >> >> >>>>>> 2.5.6.SEC03 > >> >> >>>>>> 3.0.7.RELEASE > >> >> >>>>>> > >> >> >>>>> > >> >> >>>>> Crap I think you guys shoulder consider switching to the 3.1.2 > >> >> release > >> >> >>>>> of Spring. > >> >> >>>>> As well Jetty 7.6.7, so people have the latest stable release > of > >> >> these > >> >> >>>>> 2 important pieces. > >> >> >>>>> > >> >> >>>>> > >> >> >>>>> > >> >> >>>>> > >> >> >>>>>> Cheers, > >> >> >>>>>> Jamie > >> >> >>>>>> > >> >> >>>>>> On Mon, Oct 8, 2012 at 1:09 PM, Claus Ibsen < > >> claus.ib...@gmail.com> > >> >> >>>>>> wrote: > >> >> >>>>>>> > >> >> >>>>>>> Hi > >> >> >>>>>>> > >> >> >>>>>>> What Spring version does Karaf 2.3.0 come with out of the > box? > >> >> 3.0.x > >> >> >>>>>>> or the newer 3.1.x ? > >> >> >>>>>>> > >> >> >>>>>>> On Mon, Oct 8, 2012 at 10:53 AM, Jamie G. < > >> >> jamie.goody...@gmail.com> > >> >> >>>>>>> wrote: > >> >> >>>>>>>> > >> >> >>>>>>>> I'm always ready! > >> >> >>>>>>>> > >> >> >>>>>>>> Cheers, > >> >> >>>>>>>> Jamie > >> >> >>>>>>>> > >> >> >>>>>>>> On Mon, Oct 8, 2012 at 5:08 AM, j...@nanthrax.net < > >> j...@nanthrax.net> > >> >> >>>>>>>> wrote: > >> >> >>>>>>>>> > >> >> >>>>>>>>> Great, thanks a lot ! > >> >> >&g
Re: Apache Karaf 2.3.0 very close
; >> >>> Well Camel 2.10 supports both Spring 3.0.x and 3.1.x. And we are >> >> >>> frankly only holding back because of Karaf. >> >> >>> As when people deploy Camel in Karaf they inherit the spring from >> >> Karaf. >> >> >>> >> >> >>> People in the community would like to use Spring 3.1.x as its been >> out >> >> >>> since December 2011. >> >> >>> And its the stable release path where they cut new releases. >> >> >>> >> >> >>> >> >> >>>> >> >> >>>> Regards >> >> >>>> JB >> >> >>>> >> >> >>>> On 10/08/2012 05:55 PM, Claus Ibsen wrote: >> >> >>>>> >> >> >>>>> On Mon, Oct 8, 2012 at 5:45 PM, Jamie G. < >> jamie.goody...@gmail.com> >> >> wrote: >> >> >>>>>> >> >> >>>>>> Hi Claus, >> >> >>>>>> >> >> >>>>>> From the Karaf 2.3.0 pom file: >> >> >>>>>> 1.2.1 >> >> >>>>>> 2.5.6.SEC03 >> >> >>>>>> 3.0.7.RELEASE >> >> >>>>>> >> >> >>>>> >> >> >>>>> Crap I think you guys shoulder consider switching to the 3.1.2 >> >> release >> >> >>>>> of Spring. >> >> >>>>> As well Jetty 7.6.7, so people have the latest stable release of >> >> these >> >> >>>>> 2 important pieces. >> >> >>>>> >> >> >>>>> >> >> >>>>> >> >> >>>>> >> >> >>>>>> Cheers, >> >> >>>>>> Jamie >> >> >>>>>> >> >> >>>>>> On Mon, Oct 8, 2012 at 1:09 PM, Claus Ibsen < >> claus.ib...@gmail.com> >> >> >>>>>> wrote: >> >> >>>>>>> >> >> >>>>>>> Hi >> >> >>>>>>> >> >> >>>>>>> What Spring version does Karaf 2.3.0 come with out of the box? >> >> 3.0.x >> >> >>>>>>> or the newer 3.1.x ? >> >> >>>>>>> >> >> >>>>>>> On Mon, Oct 8, 2012 at 10:53 AM, Jamie G. < >> >> jamie.goody...@gmail.com> >> >> >>>>>>> wrote: >> >> >>>>>>>> >> >> >>>>>>>> I'm always ready! >> >> >>>>>>>> >> >> >>>>>>>> Cheers, >> >> >>>>>>>> Jamie >> >> >>>>>>>> >> >> >>>>>>>> On Mon, Oct 8, 2012 at 5:08 AM, j...@nanthrax.net < >> j...@nanthrax.net> >> >> >>>>>>>> wrote: >> >> >>>>>>>>> >> >> >>>>>>>>> Great, thanks a lot ! >> >> >>>>>>>>> >> >> >>>>>>>>> -- >> >> >>>>>>>>> Jean-Baptiste Onofré >> >> >>>>>>>>> jbono...@apache.org >> >> >>>>>>>>> http://blog.nanthrax.net >> >> >>>>>>>>> Talend - http://wwx.talend.com >> >> >>>>>>>>> >> >> >>>>>>>>> - Reply message - >> >> >>>>>>>>> From: "Andreas Pieber" >> >> >>>>>>>>> To: >> >> >>>>>>>>> Subject: Apache Karaf 2.3.0 very close >> >> >>>>>>>>> Date: Mon, Oct 8, 2012 9:17 am >> >> >>>>>>>>> >> >> >>>>>>>>> >> >> >>>>>>>>> Hey, >> >> >>>>>>>>> >> >> >>>>>>>>> On Mon, Oct 8, 2012 at 7:46 AM, Jean-Baptiste Onofré < >> >> j...@nanthrax.net> >> >> >>>>>>>>> wrote: >> >> >>>>>>>>>> >> >> >>>>>>>>>> @Andreas, could you take a look on KARAF-1878 and KARAF-1752 >> >> >>>>>>>>>> (assigned to >> >> >>>>>>>>>> you) ? If you are busy today, I think we can postpone to >> 2.3.1. >> >> >>>>>>>>> >> >> >>>>>>>>> >> >> >>>>>>>>> I wanted to keep KARAF-1878 opened for review till tonight; >> I'll >> >> apply >> >> >>>>>>>>> afterwards. I'll also apply KARAF-1752 then. >> >> >>>>>>>>> >> >> >>>>>>>>> Kind regards, >> >> >>>>>>>>> Andreas >> >> >>>>>>>>> >> >> >>>>>>>>>> >> >> >>>>>>>>>> Thanks all guys, >> >> >>>>>>>>>> Regards >> >> >>>>>>>>>> JB >> >> >>>>>>>>>> -- >> >> >>>>>>>>>> Jean-Baptiste Onofré >> >> >>>>>>>>>> jbono...@apache.org >> >> >>>>>>>>>> http://blog.nanthrax.net >> >> >>>>>>>>>> Talend - http://www.talend.com >> >> >>>>>>> >> >> >>>>>>> >> >> >>>>>>> >> >> >>>>>>> >> >> >>>>>>> -- >> >> >>>>>>> Claus Ibsen >> >> >>>>>>> - >> >> >>>>>>> Red Hat, Inc. >> >> >>>>>>> FuseSource is now part of Red Hat >> >> >>>>>>> Email: cib...@redhat.com >> >> >>>>>>> Web: http://fusesource.com >> >> >>>>>>> Twitter: davsclaus >> >> >>>>>>> Blog: http://davsclaus.com >> >> >>>>>>> Author of Camel in Action: http://www.manning.com/ibsen >> >> >>>>> >> >> >>>>> >> >> >>>>> >> >> >>>>> >> >> >>>> >> >> >>>> -- >> >> >>>> Jean-Baptiste Onofré >> >> >>>> jbono...@apache.org >> >> >>>> http://blog.nanthrax.net >> >> >>>> Talend - http://www.talend.com >> >> >>> >> >> >>> >> >> >>> >> >> >> >> >> >> -- >> >> >> Jean-Baptiste Onofré >> >> >> jbono...@apache.org >> >> >> http://blog.nanthrax.net >> >> >> Talend - http://www.talend.com >> >> > >> >> > -- >> >> > Daniel Kulp >> >> > dk...@apache.org - http://dankulp.com/blog >> >> > Talend Community Coder - http://coders.talend.com >> >> > >> >> >> >> >> >> >> >> -- >> >> Claus Ibsen >> >> - >> >> Red Hat, Inc. >> >> FuseSource is now part of Red Hat >> >> Email: cib...@redhat.com >> >> Web: http://fusesource.com >> >> Twitter: davsclaus >> >> Blog: http://davsclaus.com >> >> Author of Camel in Action: http://www.manning.com/ibsen >> >> >> > >> > >> > >> > -- >> > Charles Moulliard >> > Apache Committer / Sr. Enterprise Architect (RedHat) >> > Twitter : @cmoulliard | Blog : http://cmoulliard.blogspot.com >> >> >> >> -- >> >> Apache Karaf <http://karaf.apache.org/> Committer & PMC >> OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/> >> Committer & Project Lead >> OPS4J Pax for Vaadin >> <http://team.ops4j.org/wiki/display/PAXVAADIN/Home> Commiter & Project >> Lead >> blog <http://notizblog.nierbeck.de/> >> > > > > -- > > Guillaume Nodet > > Blog: http://gnodet.blogspot.com/ > > FuseSource, Integration everywhere > http://fusesource.com
Re: Apache Karaf 2.3.0 very close
>>> > >> >>>> Regards > >> >>>> JB > >> >>>> > >> >>>> On 10/08/2012 05:55 PM, Claus Ibsen wrote: > >> >>>>> > >> >>>>> On Mon, Oct 8, 2012 at 5:45 PM, Jamie G. < > jamie.goody...@gmail.com> > >> wrote: > >> >>>>>> > >> >>>>>> Hi Claus, > >> >>>>>> > >> >>>>>> From the Karaf 2.3.0 pom file: > >> >>>>>> 1.2.1 > >> >>>>>> 2.5.6.SEC03 > >> >>>>>> 3.0.7.RELEASE > >> >>>>>> > >> >>>>> > >> >>>>> Crap I think you guys shoulder consider switching to the 3.1.2 > >> release > >> >>>>> of Spring. > >> >>>>> As well Jetty 7.6.7, so people have the latest stable release of > >> these > >> >>>>> 2 important pieces. > >> >>>>> > >> >>>>> > >> >>>>> > >> >>>>> > >> >>>>>> Cheers, > >> >>>>>> Jamie > >> >>>>>> > >> >>>>>> On Mon, Oct 8, 2012 at 1:09 PM, Claus Ibsen < > claus.ib...@gmail.com> > >> >>>>>> wrote: > >> >>>>>>> > >> >>>>>>> Hi > >> >>>>>>> > >> >>>>>>> What Spring version does Karaf 2.3.0 come with out of the box? > >> 3.0.x > >> >>>>>>> or the newer 3.1.x ? > >> >>>>>>> > >> >>>>>>> On Mon, Oct 8, 2012 at 10:53 AM, Jamie G. < > >> jamie.goody...@gmail.com> > >> >>>>>>> wrote: > >> >>>>>>>> > >> >>>>>>>> I'm always ready! > >> >>>>>>>> > >> >>>>>>>> Cheers, > >> >>>>>>>> Jamie > >> >>>>>>>> > >> >>>>>>>> On Mon, Oct 8, 2012 at 5:08 AM, j...@nanthrax.net < > j...@nanthrax.net> > >> >>>>>>>> wrote: > >> >>>>>>>>> > >> >>>>>>>>> Great, thanks a lot ! > >> >>>>>>>>> > >> >>>>>>>>> -- > >> >>>>>>>>> Jean-Baptiste Onofré > >> >>>>>>>>> jbono...@apache.org > >> >>>>>>>>> http://blog.nanthrax.net > >> >>>>>>>>> Talend - http://wwx.talend.com > >> >>>>>>>>> > >> >>>>>>>>> - Reply message - > >> >>>>>>>>> From: "Andreas Pieber" > >> >>>>>>>>> To: > >> >>>>>>>>> Subject: Apache Karaf 2.3.0 very close > >> >>>>>>>>> Date: Mon, Oct 8, 2012 9:17 am > >> >>>>>>>>> > >> >>>>>>>>> > >> >>>>>>>>> Hey, > >> >>>>>>>>> > >> >>>>>>>>> On Mon, Oct 8, 2012 at 7:46 AM, Jean-Baptiste Onofré < > >> j...@nanthrax.net> > >> >>>>>>>>> wrote: > >> >>>>>>>>>> > >> >>>>>>>>>> @Andreas, could you take a look on KARAF-1878 and KARAF-1752 > >> >>>>>>>>>> (assigned to > >> >>>>>>>>>> you) ? If you are busy today, I think we can postpone to > 2.3.1. > >> >>>>>>>>> > >> >>>>>>>>> > >> >>>>>>>>> I wanted to keep KARAF-1878 opened for review till tonight; > I'll > >> apply > >> >>>>>>>>> afterwards. I'll also apply KARAF-1752 then. > >> >>>>>>>>> > >> >>>>>>>>> Kind regards, > >> >>>>>>>>> Andreas > >> >>>>>>>>> > >> >>>>>>>>>> > >> >>>>>>>>>> Thanks all guys, > >> >>>>>>>>>> Regards > >> >>>>>>>>>> JB > >> >>>>>>>>>> -- > >> >>>>>>>>>> Jean-Baptiste Onofré > >> >>>>>>>>>> jbono...@apache.org > >> >>>>>>>>>> http://blog.nanthrax.net > >> >>>>>>>>>> Talend - http://www.talend.com > >> >>>>>>> > >> >>>>>>> > >> >>>>>>> > >> >>>>>>> > >> >>>>>>> -- > >> >>>>>>> Claus Ibsen > >> >>>>>>> - > >> >>>>>>> Red Hat, Inc. > >> >>>>>>> FuseSource is now part of Red Hat > >> >>>>>>> Email: cib...@redhat.com > >> >>>>>>> Web: http://fusesource.com > >> >>>>>>> Twitter: davsclaus > >> >>>>>>> Blog: http://davsclaus.com > >> >>>>>>> Author of Camel in Action: http://www.manning.com/ibsen > >> >>>>> > >> >>>>> > >> >>>>> > >> >>>>> > >> >>>> > >> >>>> -- > >> >>>> Jean-Baptiste Onofré > >> >>>> jbono...@apache.org > >> >>>> http://blog.nanthrax.net > >> >>>> Talend - http://www.talend.com > >> >>> > >> >>> > >> >>> > >> >> > >> >> -- > >> >> Jean-Baptiste Onofré > >> >> jbono...@apache.org > >> >> http://blog.nanthrax.net > >> >> Talend - http://www.talend.com > >> > > >> > -- > >> > Daniel Kulp > >> > dk...@apache.org - http://dankulp.com/blog > >> > Talend Community Coder - http://coders.talend.com > >> > > >> > >> > >> > >> -- > >> Claus Ibsen > >> - > >> Red Hat, Inc. > >> FuseSource is now part of Red Hat > >> Email: cib...@redhat.com > >> Web: http://fusesource.com > >> Twitter: davsclaus > >> Blog: http://davsclaus.com > >> Author of Camel in Action: http://www.manning.com/ibsen > >> > > > > > > > > -- > > Charles Moulliard > > Apache Committer / Sr. Enterprise Architect (RedHat) > > Twitter : @cmoulliard | Blog : http://cmoulliard.blogspot.com > > > > -- > > Apache Karaf <http://karaf.apache.org/> Committer & PMC > OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/> > Committer & Project Lead > OPS4J Pax for Vaadin > <http://team.ops4j.org/wiki/display/PAXVAADIN/Home> Commiter & Project > Lead > blog <http://notizblog.nierbeck.de/> > -- Guillaume Nodet Blog: http://gnodet.blogspot.com/ FuseSource, Integration everywhere http://fusesource.com
Re: Apache Karaf 2.3.0 very close
I think a valid "workaround" would be to offer a spring31 feature, I'm quite sure we're able to extract that kind of feature from trunk ;) regarding the road-map proposal, yes this would be really helpful. I know we have a Matrix showing which version does contain which dependencies (@Jamie where is it located?) but somehow it's again a pain to find it. I think we need to redo our webpage desperately since not all information can be found easily and the menu doesn't necessarily relate to the content (e.g. the manual) regards, Achim 2012/10/9 Charles Moulliard : > Even if I understand the karaf position I completely agree about Claus's > remark to also have Spring 3.1 for Camel and others projects. > > What I would like to propose is that we create for Karaf/ServiceMix > projects a page containing a table of the different software used and have > a roadmap about them. This question is important not only for Spring > framework but also Pax, Aries, Felix, ... which are (re)packaged into > Karaf/ServiceMix > This will avoid that we discover a few days before the publication of a > release that we have miss something > > Just my 5€ cents. > > On Tue, Oct 9, 2012 at 8:19 AM, Claus Ibsen wrote: > >> On Mon, Oct 8, 2012 at 7:30 PM, Daniel Kulp wrote: >> > >> > On Oct 8, 2012, at 1:08 PM, Jean-Baptiste Onofré >> wrote: >> > >> >> Agree Claus, but Camel is not the only application running on Karaf. >> >> >> >> So, we have to think about "others projects" as well. >> >> >> >> I have no problem to upgrade to Spring 3.1.x but later (why not imagine >> a Karaf 2.4.x for that, it could be a good indicator), and propose both >> Spring 3.0 and 3.1 in Karaf 2.3.0 (depending of the impact, that I gonna >> test tonight). >> > >> > I agree with that.I know CXF has had very little testing with Spring >> 3.1.x.I would definitely prefer keeping on 3.0.7 for Karaf 2.3 and >> think about that for 2.4. >> > >> > I also agree that this is way to close to "release" to flip out a major >> component like spring. Maybe a month ago, but not now. >> > >> >> Yeah I can understand the deadline issue as well. >> >> But its a shame that the new shiny Karaf 2.3.0 comes out of the box >> with the old Spring 3.0.7 from Dec 2011. And there has not been any >> new releases of Spring 3.0.x since. >> >> It would be cool if it was possible to provide an easy way for people >> to switch Karaf to offer Spring 3.1. >> Maybe that requires to offer a spring31 feature, and an easy way for >> people to configure Karaf to use that. >> >> At Camel we have a CI job that tests Camel with Spring 3.1. The >> upgrade for Camel has been painless. >> >> >> > >> > Dan >> > >> > >> > >> > >> >> >> >> Regards >> >> JB >> >> >> >> On 10/08/2012 06:48 PM, Claus Ibsen wrote: >> >>> On Mon, Oct 8, 2012 at 6:44 PM, Jean-Baptiste Onofré >> wrote: >> >>>> Camel 2.10.x uses Spring 3.0.7 for now, for we are "aligned" with >> Camel >> >>>> 2.10. >> >>>> >> >>>> Does it make sense to update to Spring 3.1.x (for future Camel version >> >>>> maybe) ? >> >>>> >> >>> >> >>> Well Camel 2.10 supports both Spring 3.0.x and 3.1.x. And we are >> >>> frankly only holding back because of Karaf. >> >>> As when people deploy Camel in Karaf they inherit the spring from >> Karaf. >> >>> >> >>> People in the community would like to use Spring 3.1.x as its been out >> >>> since December 2011. >> >>> And its the stable release path where they cut new releases. >> >>> >> >>> >> >>>> >> >>>> Regards >> >>>> JB >> >>>> >> >>>> On 10/08/2012 05:55 PM, Claus Ibsen wrote: >> >>>>> >> >>>>> On Mon, Oct 8, 2012 at 5:45 PM, Jamie G. >> wrote: >> >>>>>> >> >>>>>> Hi Claus, >> >>>>>> >> >>>>>> From the Karaf 2.3.0 pom file: >> >>>>>> 1.2.1 >> >>>>>> 2.5.6.SEC03 >> >>>>>> 3.0.7.RELEASE >> >>>>>> >> >>>>> >> >>>>> Crap I think you guys shoulder consi
Re: Apache Karaf 2.3.0 very close
We provide such kind of version matrix in the release notes, but it's a good idea to have a wiki page that track this (including the major versions alignment, Jira ID for the dependency upgrade, etc). Anyway, for 2.3.0, I'm working on a spring31 feature. Regards JB On 10/09/2012 08:53 AM, Charles Moulliard wrote: Even if I understand the karaf position I completely agree about Claus's remark to also have Spring 3.1 for Camel and others projects. What I would like to propose is that we create for Karaf/ServiceMix projects a page containing a table of the different software used and have a roadmap about them. This question is important not only for Spring framework but also Pax, Aries, Felix, ... which are (re)packaged into Karaf/ServiceMix This will avoid that we discover a few days before the publication of a release that we have miss something Just my 5€ cents. On Tue, Oct 9, 2012 at 8:19 AM, Claus Ibsen wrote: On Mon, Oct 8, 2012 at 7:30 PM, Daniel Kulp wrote: On Oct 8, 2012, at 1:08 PM, Jean-Baptiste Onofré wrote: Agree Claus, but Camel is not the only application running on Karaf. So, we have to think about "others projects" as well. I have no problem to upgrade to Spring 3.1.x but later (why not imagine a Karaf 2.4.x for that, it could be a good indicator), and propose both Spring 3.0 and 3.1 in Karaf 2.3.0 (depending of the impact, that I gonna test tonight). I agree with that.I know CXF has had very little testing with Spring 3.1.x.I would definitely prefer keeping on 3.0.7 for Karaf 2.3 and think about that for 2.4. I also agree that this is way to close to "release" to flip out a major component like spring. Maybe a month ago, but not now. Yeah I can understand the deadline issue as well. But its a shame that the new shiny Karaf 2.3.0 comes out of the box with the old Spring 3.0.7 from Dec 2011. And there has not been any new releases of Spring 3.0.x since. It would be cool if it was possible to provide an easy way for people to switch Karaf to offer Spring 3.1. Maybe that requires to offer a spring31 feature, and an easy way for people to configure Karaf to use that. At Camel we have a CI job that tests Camel with Spring 3.1. The upgrade for Camel has been painless. Dan Regards JB On 10/08/2012 06:48 PM, Claus Ibsen wrote: On Mon, Oct 8, 2012 at 6:44 PM, Jean-Baptiste Onofré wrote: Camel 2.10.x uses Spring 3.0.7 for now, for we are "aligned" with Camel 2.10. Does it make sense to update to Spring 3.1.x (for future Camel version maybe) ? Well Camel 2.10 supports both Spring 3.0.x and 3.1.x. And we are frankly only holding back because of Karaf. As when people deploy Camel in Karaf they inherit the spring from Karaf. People in the community would like to use Spring 3.1.x as its been out since December 2011. And its the stable release path where they cut new releases. Regards JB On 10/08/2012 05:55 PM, Claus Ibsen wrote: On Mon, Oct 8, 2012 at 5:45 PM, Jamie G. wrote: Hi Claus, From the Karaf 2.3.0 pom file: 1.2.1 2.5.6.SEC03 3.0.7.RELEASE Crap I think you guys shoulder consider switching to the 3.1.2 release of Spring. As well Jetty 7.6.7, so people have the latest stable release of these 2 important pieces. Cheers, Jamie On Mon, Oct 8, 2012 at 1:09 PM, Claus Ibsen wrote: Hi What Spring version does Karaf 2.3.0 come with out of the box? 3.0.x or the newer 3.1.x ? On Mon, Oct 8, 2012 at 10:53 AM, Jamie G. < jamie.goody...@gmail.com> wrote: I'm always ready! Cheers, Jamie On Mon, Oct 8, 2012 at 5:08 AM, j...@nanthrax.net wrote: Great, thanks a lot ! -- Jean-Baptiste Onofré jbono...@apache.org http://blog.nanthrax.net Talend - http://wwx.talend.com - Reply message - From: "Andreas Pieber" To: Subject: Apache Karaf 2.3.0 very close Date: Mon, Oct 8, 2012 9:17 am Hey, On Mon, Oct 8, 2012 at 7:46 AM, Jean-Baptiste Onofré < j...@nanthrax.net> wrote: @Andreas, could you take a look on KARAF-1878 and KARAF-1752 (assigned to you) ? If you are busy today, I think we can postpone to 2.3.1. I wanted to keep KARAF-1878 opened for review till tonight; I'll apply afterwards. I'll also apply KARAF-1752 then. Kind regards, Andreas Thanks all guys, Regards JB -- Jean-Baptiste Onofré jbono...@apache.org http://blog.nanthrax.net Talend - http://www.talend.com -- Claus Ibsen - Red Hat, Inc. FuseSource is now part of Red Hat Email: cib...@redhat.com Web: http://fusesource.com Twitter: davsclaus Blog: http://davsclaus.com Author of Camel in Action: http://www.manning.com/ibsen -- Jean-Baptiste Onofré jbono...@apache.org http://blog.nanthrax.net Talend - http://www.talend.com -- Jean-Baptiste Onofré jbono...@apache.org http://blog.nanthrax.net Talend - http://www.talend.com -- Daniel Kulp dk...@apache.org - http://dankulp.com/blog Talend Community Coder - http://c
Re: Apache Karaf 2.3.0 very close
Even if I understand the karaf position I completely agree about Claus's remark to also have Spring 3.1 for Camel and others projects. What I would like to propose is that we create for Karaf/ServiceMix projects a page containing a table of the different software used and have a roadmap about them. This question is important not only for Spring framework but also Pax, Aries, Felix, ... which are (re)packaged into Karaf/ServiceMix This will avoid that we discover a few days before the publication of a release that we have miss something Just my 5€ cents. On Tue, Oct 9, 2012 at 8:19 AM, Claus Ibsen wrote: > On Mon, Oct 8, 2012 at 7:30 PM, Daniel Kulp wrote: > > > > On Oct 8, 2012, at 1:08 PM, Jean-Baptiste Onofré > wrote: > > > >> Agree Claus, but Camel is not the only application running on Karaf. > >> > >> So, we have to think about "others projects" as well. > >> > >> I have no problem to upgrade to Spring 3.1.x but later (why not imagine > a Karaf 2.4.x for that, it could be a good indicator), and propose both > Spring 3.0 and 3.1 in Karaf 2.3.0 (depending of the impact, that I gonna > test tonight). > > > > I agree with that.I know CXF has had very little testing with Spring > 3.1.x.I would definitely prefer keeping on 3.0.7 for Karaf 2.3 and > think about that for 2.4. > > > > I also agree that this is way to close to "release" to flip out a major > component like spring. Maybe a month ago, but not now. > > > > Yeah I can understand the deadline issue as well. > > But its a shame that the new shiny Karaf 2.3.0 comes out of the box > with the old Spring 3.0.7 from Dec 2011. And there has not been any > new releases of Spring 3.0.x since. > > It would be cool if it was possible to provide an easy way for people > to switch Karaf to offer Spring 3.1. > Maybe that requires to offer a spring31 feature, and an easy way for > people to configure Karaf to use that. > > At Camel we have a CI job that tests Camel with Spring 3.1. The > upgrade for Camel has been painless. > > > > > > Dan > > > > > > > > > >> > >> Regards > >> JB > >> > >> On 10/08/2012 06:48 PM, Claus Ibsen wrote: > >>> On Mon, Oct 8, 2012 at 6:44 PM, Jean-Baptiste Onofré > wrote: > >>>> Camel 2.10.x uses Spring 3.0.7 for now, for we are "aligned" with > Camel > >>>> 2.10. > >>>> > >>>> Does it make sense to update to Spring 3.1.x (for future Camel version > >>>> maybe) ? > >>>> > >>> > >>> Well Camel 2.10 supports both Spring 3.0.x and 3.1.x. And we are > >>> frankly only holding back because of Karaf. > >>> As when people deploy Camel in Karaf they inherit the spring from > Karaf. > >>> > >>> People in the community would like to use Spring 3.1.x as its been out > >>> since December 2011. > >>> And its the stable release path where they cut new releases. > >>> > >>> > >>>> > >>>> Regards > >>>> JB > >>>> > >>>> On 10/08/2012 05:55 PM, Claus Ibsen wrote: > >>>>> > >>>>> On Mon, Oct 8, 2012 at 5:45 PM, Jamie G. > wrote: > >>>>>> > >>>>>> Hi Claus, > >>>>>> > >>>>>> From the Karaf 2.3.0 pom file: > >>>>>> 1.2.1 > >>>>>> 2.5.6.SEC03 > >>>>>> 3.0.7.RELEASE > >>>>>> > >>>>> > >>>>> Crap I think you guys shoulder consider switching to the 3.1.2 > release > >>>>> of Spring. > >>>>> As well Jetty 7.6.7, so people have the latest stable release of > these > >>>>> 2 important pieces. > >>>>> > >>>>> > >>>>> > >>>>> > >>>>>> Cheers, > >>>>>> Jamie > >>>>>> > >>>>>> On Mon, Oct 8, 2012 at 1:09 PM, Claus Ibsen > >>>>>> wrote: > >>>>>>> > >>>>>>> Hi > >>>>>>> > >>>>>>> What Spring version does Karaf 2.3.0 come with out of the box? > 3.0.x > >>>>>>> or the newer 3.1.x ? > >>>>>>> > >>>>>>> On Mon, Oct 8, 2012 at 10:53 AM, Jamie G. < > jamie.goody...@gmail.com> > >>>>>>
Re: Apache Karaf 2.3.0 very close
On Mon, Oct 8, 2012 at 7:30 PM, Daniel Kulp wrote: > > On Oct 8, 2012, at 1:08 PM, Jean-Baptiste Onofré wrote: > >> Agree Claus, but Camel is not the only application running on Karaf. >> >> So, we have to think about "others projects" as well. >> >> I have no problem to upgrade to Spring 3.1.x but later (why not imagine a >> Karaf 2.4.x for that, it could be a good indicator), and propose both Spring >> 3.0 and 3.1 in Karaf 2.3.0 (depending of the impact, that I gonna test >> tonight). > > I agree with that.I know CXF has had very little testing with Spring > 3.1.x.I would definitely prefer keeping on 3.0.7 for Karaf 2.3 and think > about that for 2.4. > > I also agree that this is way to close to "release" to flip out a major > component like spring. Maybe a month ago, but not now. > Yeah I can understand the deadline issue as well. But its a shame that the new shiny Karaf 2.3.0 comes out of the box with the old Spring 3.0.7 from Dec 2011. And there has not been any new releases of Spring 3.0.x since. It would be cool if it was possible to provide an easy way for people to switch Karaf to offer Spring 3.1. Maybe that requires to offer a spring31 feature, and an easy way for people to configure Karaf to use that. At Camel we have a CI job that tests Camel with Spring 3.1. The upgrade for Camel has been painless. > > Dan > > > > >> >> Regards >> JB >> >> On 10/08/2012 06:48 PM, Claus Ibsen wrote: >>> On Mon, Oct 8, 2012 at 6:44 PM, Jean-Baptiste Onofré >>> wrote: >>>> Camel 2.10.x uses Spring 3.0.7 for now, for we are "aligned" with Camel >>>> 2.10. >>>> >>>> Does it make sense to update to Spring 3.1.x (for future Camel version >>>> maybe) ? >>>> >>> >>> Well Camel 2.10 supports both Spring 3.0.x and 3.1.x. And we are >>> frankly only holding back because of Karaf. >>> As when people deploy Camel in Karaf they inherit the spring from Karaf. >>> >>> People in the community would like to use Spring 3.1.x as its been out >>> since December 2011. >>> And its the stable release path where they cut new releases. >>> >>> >>>> >>>> Regards >>>> JB >>>> >>>> On 10/08/2012 05:55 PM, Claus Ibsen wrote: >>>>> >>>>> On Mon, Oct 8, 2012 at 5:45 PM, Jamie G. wrote: >>>>>> >>>>>> Hi Claus, >>>>>> >>>>>> From the Karaf 2.3.0 pom file: >>>>>> 1.2.1 >>>>>> 2.5.6.SEC03 >>>>>> 3.0.7.RELEASE >>>>>> >>>>> >>>>> Crap I think you guys shoulder consider switching to the 3.1.2 release >>>>> of Spring. >>>>> As well Jetty 7.6.7, so people have the latest stable release of these >>>>> 2 important pieces. >>>>> >>>>> >>>>> >>>>> >>>>>> Cheers, >>>>>> Jamie >>>>>> >>>>>> On Mon, Oct 8, 2012 at 1:09 PM, Claus Ibsen >>>>>> wrote: >>>>>>> >>>>>>> Hi >>>>>>> >>>>>>> What Spring version does Karaf 2.3.0 come with out of the box? 3.0.x >>>>>>> or the newer 3.1.x ? >>>>>>> >>>>>>> On Mon, Oct 8, 2012 at 10:53 AM, Jamie G. >>>>>>> wrote: >>>>>>>> >>>>>>>> I'm always ready! >>>>>>>> >>>>>>>> Cheers, >>>>>>>> Jamie >>>>>>>> >>>>>>>> On Mon, Oct 8, 2012 at 5:08 AM, j...@nanthrax.net >>>>>>>> wrote: >>>>>>>>> >>>>>>>>> Great, thanks a lot ! >>>>>>>>> >>>>>>>>> -- >>>>>>>>> Jean-Baptiste Onofré >>>>>>>>> jbono...@apache.org >>>>>>>>> http://blog.nanthrax.net >>>>>>>>> Talend - http://wwx.talend.com >>>>>>>>> >>>>>>>>> - Reply message - >>>>>>>>> From: "Andreas Pieber" >>>>>>>>> To: >>>>>>>>> Subject: Apache Karaf 2.3.0 very close >>>>>>>>> Date: Mon, Oct 8, 2012 9:17 am >>>&
Re: Apache Karaf 2.3.0 very close
On Oct 8, 2012, at 1:08 PM, Jean-Baptiste Onofré wrote: > Agree Claus, but Camel is not the only application running on Karaf. > > So, we have to think about "others projects" as well. > > I have no problem to upgrade to Spring 3.1.x but later (why not imagine a > Karaf 2.4.x for that, it could be a good indicator), and propose both Spring > 3.0 and 3.1 in Karaf 2.3.0 (depending of the impact, that I gonna test > tonight). I agree with that.I know CXF has had very little testing with Spring 3.1.x. I would definitely prefer keeping on 3.0.7 for Karaf 2.3 and think about that for 2.4. I also agree that this is way to close to "release" to flip out a major component like spring. Maybe a month ago, but not now. Dan > > Regards > JB > > On 10/08/2012 06:48 PM, Claus Ibsen wrote: >> On Mon, Oct 8, 2012 at 6:44 PM, Jean-Baptiste Onofré >> wrote: >>> Camel 2.10.x uses Spring 3.0.7 for now, for we are "aligned" with Camel >>> 2.10. >>> >>> Does it make sense to update to Spring 3.1.x (for future Camel version >>> maybe) ? >>> >> >> Well Camel 2.10 supports both Spring 3.0.x and 3.1.x. And we are >> frankly only holding back because of Karaf. >> As when people deploy Camel in Karaf they inherit the spring from Karaf. >> >> People in the community would like to use Spring 3.1.x as its been out >> since December 2011. >> And its the stable release path where they cut new releases. >> >> >>> >>> Regards >>> JB >>> >>> On 10/08/2012 05:55 PM, Claus Ibsen wrote: >>>> >>>> On Mon, Oct 8, 2012 at 5:45 PM, Jamie G. wrote: >>>>> >>>>> Hi Claus, >>>>> >>>>> From the Karaf 2.3.0 pom file: >>>>> 1.2.1 >>>>> 2.5.6.SEC03 >>>>> 3.0.7.RELEASE >>>>> >>>> >>>> Crap I think you guys shoulder consider switching to the 3.1.2 release >>>> of Spring. >>>> As well Jetty 7.6.7, so people have the latest stable release of these >>>> 2 important pieces. >>>> >>>> >>>> >>>> >>>>> Cheers, >>>>> Jamie >>>>> >>>>> On Mon, Oct 8, 2012 at 1:09 PM, Claus Ibsen >>>>> wrote: >>>>>> >>>>>> Hi >>>>>> >>>>>> What Spring version does Karaf 2.3.0 come with out of the box? 3.0.x >>>>>> or the newer 3.1.x ? >>>>>> >>>>>> On Mon, Oct 8, 2012 at 10:53 AM, Jamie G. >>>>>> wrote: >>>>>>> >>>>>>> I'm always ready! >>>>>>> >>>>>>> Cheers, >>>>>>> Jamie >>>>>>> >>>>>>> On Mon, Oct 8, 2012 at 5:08 AM, j...@nanthrax.net >>>>>>> wrote: >>>>>>>> >>>>>>>> Great, thanks a lot ! >>>>>>>> >>>>>>>> -- >>>>>>>> Jean-Baptiste Onofré >>>>>>>> jbono...@apache.org >>>>>>>> http://blog.nanthrax.net >>>>>>>> Talend - http://wwx.talend.com >>>>>>>> >>>>>>>> - Reply message - >>>>>>>> From: "Andreas Pieber" >>>>>>>> To: >>>>>>>> Subject: Apache Karaf 2.3.0 very close >>>>>>>> Date: Mon, Oct 8, 2012 9:17 am >>>>>>>> >>>>>>>> >>>>>>>> Hey, >>>>>>>> >>>>>>>> On Mon, Oct 8, 2012 at 7:46 AM, Jean-Baptiste Onofré >>>>>>>> >>>>>>>> wrote: >>>>>>>>> >>>>>>>>> @Andreas, could you take a look on KARAF-1878 and KARAF-1752 >>>>>>>>> (assigned to >>>>>>>>> you) ? If you are busy today, I think we can postpone to 2.3.1. >>>>>>>> >>>>>>>> >>>>>>>> I wanted to keep KARAF-1878 opened for review till tonight; I'll apply >>>>>>>> afterwards. I'll also apply KARAF-1752 then. >>>>>>>> >>>>>>>> Kind regards, >>>>>>>> Andreas >>>>>>>> >>>>>>>>> >>>>>>>>> Thanks all guys, >>>>>>>>> Regards >>>>>>>>> JB >>>>>>>>> -- >>>>>>>>> Jean-Baptiste Onofré >>>>>>>>> jbono...@apache.org >>>>>>>>> http://blog.nanthrax.net >>>>>>>>> Talend - http://www.talend.com >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> Claus Ibsen >>>>>> - >>>>>> Red Hat, Inc. >>>>>> FuseSource is now part of Red Hat >>>>>> Email: cib...@redhat.com >>>>>> Web: http://fusesource.com >>>>>> Twitter: davsclaus >>>>>> Blog: http://davsclaus.com >>>>>> Author of Camel in Action: http://www.manning.com/ibsen >>>> >>>> >>>> >>>> >>> >>> -- >>> Jean-Baptiste Onofré >>> jbono...@apache.org >>> http://blog.nanthrax.net >>> Talend - http://www.talend.com >> >> >> > > -- > Jean-Baptiste Onofré > jbono...@apache.org > http://blog.nanthrax.net > Talend - http://www.talend.com -- Daniel Kulp dk...@apache.org - http://dankulp.com/blog Talend Community Coder - http://coders.talend.com
Re: Apache Karaf 2.3.0 very close
Agree Claus, but Camel is not the only application running on Karaf. So, we have to think about "others projects" as well. I have no problem to upgrade to Spring 3.1.x but later (why not imagine a Karaf 2.4.x for that, it could be a good indicator), and propose both Spring 3.0 and 3.1 in Karaf 2.3.0 (depending of the impact, that I gonna test tonight). Regards JB On 10/08/2012 06:48 PM, Claus Ibsen wrote: On Mon, Oct 8, 2012 at 6:44 PM, Jean-Baptiste Onofré wrote: Camel 2.10.x uses Spring 3.0.7 for now, for we are "aligned" with Camel 2.10. Does it make sense to update to Spring 3.1.x (for future Camel version maybe) ? Well Camel 2.10 supports both Spring 3.0.x and 3.1.x. And we are frankly only holding back because of Karaf. As when people deploy Camel in Karaf they inherit the spring from Karaf. People in the community would like to use Spring 3.1.x as its been out since December 2011. And its the stable release path where they cut new releases. Regards JB On 10/08/2012 05:55 PM, Claus Ibsen wrote: On Mon, Oct 8, 2012 at 5:45 PM, Jamie G. wrote: Hi Claus, From the Karaf 2.3.0 pom file: 1.2.1 2.5.6.SEC03 3.0.7.RELEASE Crap I think you guys shoulder consider switching to the 3.1.2 release of Spring. As well Jetty 7.6.7, so people have the latest stable release of these 2 important pieces. Cheers, Jamie On Mon, Oct 8, 2012 at 1:09 PM, Claus Ibsen wrote: Hi What Spring version does Karaf 2.3.0 come with out of the box? 3.0.x or the newer 3.1.x ? On Mon, Oct 8, 2012 at 10:53 AM, Jamie G. wrote: I'm always ready! Cheers, Jamie On Mon, Oct 8, 2012 at 5:08 AM, j...@nanthrax.net wrote: Great, thanks a lot ! -- Jean-Baptiste Onofré jbono...@apache.org http://blog.nanthrax.net Talend - http://wwx.talend.com - Reply message - From: "Andreas Pieber" To: Subject: Apache Karaf 2.3.0 very close Date: Mon, Oct 8, 2012 9:17 am Hey, On Mon, Oct 8, 2012 at 7:46 AM, Jean-Baptiste Onofré wrote: @Andreas, could you take a look on KARAF-1878 and KARAF-1752 (assigned to you) ? If you are busy today, I think we can postpone to 2.3.1. I wanted to keep KARAF-1878 opened for review till tonight; I'll apply afterwards. I'll also apply KARAF-1752 then. Kind regards, Andreas Thanks all guys, Regards JB -- Jean-Baptiste Onofré jbono...@apache.org http://blog.nanthrax.net Talend - http://www.talend.com -- Claus Ibsen - Red Hat, Inc. FuseSource is now part of Red Hat Email: cib...@redhat.com Web: http://fusesource.com Twitter: davsclaus Blog: http://davsclaus.com Author of Camel in Action: http://www.manning.com/ibsen -- Jean-Baptiste Onofré jbono...@apache.org http://blog.nanthrax.net Talend - http://www.talend.com -- Jean-Baptiste Onofré jbono...@apache.org http://blog.nanthrax.net Talend - http://www.talend.com
Re: Apache Karaf 2.3.0 very close
On Mon, Oct 8, 2012 at 6:44 PM, Jean-Baptiste Onofré wrote: > Camel 2.10.x uses Spring 3.0.7 for now, for we are "aligned" with Camel > 2.10. > > Does it make sense to update to Spring 3.1.x (for future Camel version > maybe) ? > Well Camel 2.10 supports both Spring 3.0.x and 3.1.x. And we are frankly only holding back because of Karaf. As when people deploy Camel in Karaf they inherit the spring from Karaf. People in the community would like to use Spring 3.1.x as its been out since December 2011. And its the stable release path where they cut new releases. > > Regards > JB > > On 10/08/2012 05:55 PM, Claus Ibsen wrote: >> >> On Mon, Oct 8, 2012 at 5:45 PM, Jamie G. wrote: >>> >>> Hi Claus, >>> >>> From the Karaf 2.3.0 pom file: >>> 1.2.1 >>> 2.5.6.SEC03 >>> 3.0.7.RELEASE >>> >> >> Crap I think you guys shoulder consider switching to the 3.1.2 release >> of Spring. >> As well Jetty 7.6.7, so people have the latest stable release of these >> 2 important pieces. >> >> >> >> >>> Cheers, >>> Jamie >>> >>> On Mon, Oct 8, 2012 at 1:09 PM, Claus Ibsen >>> wrote: >>>> >>>> Hi >>>> >>>> What Spring version does Karaf 2.3.0 come with out of the box? 3.0.x >>>> or the newer 3.1.x ? >>>> >>>> On Mon, Oct 8, 2012 at 10:53 AM, Jamie G. >>>> wrote: >>>>> >>>>> I'm always ready! >>>>> >>>>> Cheers, >>>>> Jamie >>>>> >>>>> On Mon, Oct 8, 2012 at 5:08 AM, j...@nanthrax.net >>>>> wrote: >>>>>> >>>>>> Great, thanks a lot ! >>>>>> >>>>>> -- >>>>>> Jean-Baptiste Onofré >>>>>> jbono...@apache.org >>>>>> http://blog.nanthrax.net >>>>>> Talend - http://wwx.talend.com >>>>>> >>>>>> - Reply message - >>>>>> From: "Andreas Pieber" >>>>>> To: >>>>>> Subject: Apache Karaf 2.3.0 very close >>>>>> Date: Mon, Oct 8, 2012 9:17 am >>>>>> >>>>>> >>>>>> Hey, >>>>>> >>>>>> On Mon, Oct 8, 2012 at 7:46 AM, Jean-Baptiste Onofré >>>>>> wrote: >>>>>>> >>>>>>> @Andreas, could you take a look on KARAF-1878 and KARAF-1752 >>>>>>> (assigned to >>>>>>> you) ? If you are busy today, I think we can postpone to 2.3.1. >>>>>> >>>>>> >>>>>> I wanted to keep KARAF-1878 opened for review till tonight; I'll apply >>>>>> afterwards. I'll also apply KARAF-1752 then. >>>>>> >>>>>> Kind regards, >>>>>> Andreas >>>>>> >>>>>>> >>>>>>> Thanks all guys, >>>>>>> Regards >>>>>>> JB >>>>>>> -- >>>>>>> Jean-Baptiste Onofré >>>>>>> jbono...@apache.org >>>>>>> http://blog.nanthrax.net >>>>>>> Talend - http://www.talend.com >>>> >>>> >>>> >>>> >>>> -- >>>> Claus Ibsen >>>> - >>>> Red Hat, Inc. >>>> FuseSource is now part of Red Hat >>>> Email: cib...@redhat.com >>>> Web: http://fusesource.com >>>> Twitter: davsclaus >>>> Blog: http://davsclaus.com >>>> Author of Camel in Action: http://www.manning.com/ibsen >> >> >> >> > > -- > Jean-Baptiste Onofré > jbono...@apache.org > http://blog.nanthrax.net > Talend - http://www.talend.com -- Claus Ibsen - Red Hat, Inc. FuseSource is now part of Red Hat Email: cib...@redhat.com Web: http://fusesource.com Twitter: davsclaus Blog: http://davsclaus.com Author of Camel in Action: http://www.manning.com/ibsen
Re: Apache Karaf 2.3.0 very close
Can we do an update to Spring 3.1.x later on with the 2.3.x branch or would it be too disruptive? On Mon, Oct 8, 2012 at 2:14 PM, Jean-Baptiste Onofré wrote: > Camel 2.10.x uses Spring 3.0.7 for now, for we are "aligned" with Camel > 2.10. > > Does it make sense to update to Spring 3.1.x (for future Camel version > maybe) ? > > > Regards > JB > > On 10/08/2012 05:55 PM, Claus Ibsen wrote: >> >> On Mon, Oct 8, 2012 at 5:45 PM, Jamie G. wrote: >>> >>> Hi Claus, >>> >>> From the Karaf 2.3.0 pom file: >>> 1.2.1 >>> 2.5.6.SEC03 >>> 3.0.7.RELEASE >>> >> >> Crap I think you guys shoulder consider switching to the 3.1.2 release >> of Spring. >> As well Jetty 7.6.7, so people have the latest stable release of these >> 2 important pieces. >> >> >> >> >>> Cheers, >>> Jamie >>> >>> On Mon, Oct 8, 2012 at 1:09 PM, Claus Ibsen >>> wrote: >>>> >>>> Hi >>>> >>>> What Spring version does Karaf 2.3.0 come with out of the box? 3.0.x >>>> or the newer 3.1.x ? >>>> >>>> On Mon, Oct 8, 2012 at 10:53 AM, Jamie G. >>>> wrote: >>>>> >>>>> I'm always ready! >>>>> >>>>> Cheers, >>>>> Jamie >>>>> >>>>> On Mon, Oct 8, 2012 at 5:08 AM, j...@nanthrax.net >>>>> wrote: >>>>>> >>>>>> Great, thanks a lot ! >>>>>> >>>>>> -- >>>>>> Jean-Baptiste Onofré >>>>>> jbono...@apache.org >>>>>> http://blog.nanthrax.net >>>>>> Talend - http://wwx.talend.com >>>>>> >>>>>> - Reply message - >>>>>> From: "Andreas Pieber" >>>>>> To: >>>>>> Subject: Apache Karaf 2.3.0 very close >>>>>> Date: Mon, Oct 8, 2012 9:17 am >>>>>> >>>>>> >>>>>> Hey, >>>>>> >>>>>> On Mon, Oct 8, 2012 at 7:46 AM, Jean-Baptiste Onofré >>>>>> wrote: >>>>>>> >>>>>>> @Andreas, could you take a look on KARAF-1878 and KARAF-1752 >>>>>>> (assigned to >>>>>>> you) ? If you are busy today, I think we can postpone to 2.3.1. >>>>>> >>>>>> >>>>>> I wanted to keep KARAF-1878 opened for review till tonight; I'll apply >>>>>> afterwards. I'll also apply KARAF-1752 then. >>>>>> >>>>>> Kind regards, >>>>>> Andreas >>>>>> >>>>>>> >>>>>>> Thanks all guys, >>>>>>> Regards >>>>>>> JB >>>>>>> -- >>>>>>> Jean-Baptiste Onofré >>>>>>> jbono...@apache.org >>>>>>> http://blog.nanthrax.net >>>>>>> Talend - http://www.talend.com >>>> >>>> >>>> >>>> >>>> -- >>>> Claus Ibsen >>>> - >>>> Red Hat, Inc. >>>> FuseSource is now part of Red Hat >>>> Email: cib...@redhat.com >>>> Web: http://fusesource.com >>>> Twitter: davsclaus >>>> Blog: http://davsclaus.com >>>> Author of Camel in Action: http://www.manning.com/ibsen >> >> >> >> > > -- > Jean-Baptiste Onofré > jbono...@apache.org > http://blog.nanthrax.net > Talend - http://www.talend.com
Re: Apache Karaf 2.3.0 very close
Why not adding spring/3.1 "optional" feature in Karaf 2.3.0 but let spring 3.0.7 as "default" spring feature ? I think it's a good compromise. Regards JB On 10/08/2012 05:55 PM, Claus Ibsen wrote: On Mon, Oct 8, 2012 at 5:45 PM, Jamie G. wrote: Hi Claus, From the Karaf 2.3.0 pom file: 1.2.1 2.5.6.SEC03 3.0.7.RELEASE Crap I think you guys shoulder consider switching to the 3.1.2 release of Spring. As well Jetty 7.6.7, so people have the latest stable release of these 2 important pieces. Cheers, Jamie On Mon, Oct 8, 2012 at 1:09 PM, Claus Ibsen wrote: Hi What Spring version does Karaf 2.3.0 come with out of the box? 3.0.x or the newer 3.1.x ? On Mon, Oct 8, 2012 at 10:53 AM, Jamie G. wrote: I'm always ready! Cheers, Jamie On Mon, Oct 8, 2012 at 5:08 AM, j...@nanthrax.net wrote: Great, thanks a lot ! -- Jean-Baptiste Onofré jbono...@apache.org http://blog.nanthrax.net Talend - http://wwx.talend.com - Reply message - From: "Andreas Pieber" To: Subject: Apache Karaf 2.3.0 very close Date: Mon, Oct 8, 2012 9:17 am Hey, On Mon, Oct 8, 2012 at 7:46 AM, Jean-Baptiste Onofré wrote: @Andreas, could you take a look on KARAF-1878 and KARAF-1752 (assigned to you) ? If you are busy today, I think we can postpone to 2.3.1. I wanted to keep KARAF-1878 opened for review till tonight; I'll apply afterwards. I'll also apply KARAF-1752 then. Kind regards, Andreas Thanks all guys, Regards JB -- Jean-Baptiste Onofré jbono...@apache.org http://blog.nanthrax.net Talend - http://www.talend.com -- Claus Ibsen - Red Hat, Inc. FuseSource is now part of Red Hat Email: cib...@redhat.com Web: http://fusesource.com Twitter: davsclaus Blog: http://davsclaus.com Author of Camel in Action: http://www.manning.com/ibsen -- Jean-Baptiste Onofré jbono...@apache.org http://blog.nanthrax.net Talend - http://www.talend.com
Re: Apache Karaf 2.3.0 very close
Camel 2.10.x uses Spring 3.0.7 for now, for we are "aligned" with Camel 2.10. Does it make sense to update to Spring 3.1.x (for future Camel version maybe) ? Regards JB On 10/08/2012 05:55 PM, Claus Ibsen wrote: On Mon, Oct 8, 2012 at 5:45 PM, Jamie G. wrote: Hi Claus, From the Karaf 2.3.0 pom file: 1.2.1 2.5.6.SEC03 3.0.7.RELEASE Crap I think you guys shoulder consider switching to the 3.1.2 release of Spring. As well Jetty 7.6.7, so people have the latest stable release of these 2 important pieces. Cheers, Jamie On Mon, Oct 8, 2012 at 1:09 PM, Claus Ibsen wrote: Hi What Spring version does Karaf 2.3.0 come with out of the box? 3.0.x or the newer 3.1.x ? On Mon, Oct 8, 2012 at 10:53 AM, Jamie G. wrote: I'm always ready! Cheers, Jamie On Mon, Oct 8, 2012 at 5:08 AM, j...@nanthrax.net wrote: Great, thanks a lot ! -- Jean-Baptiste Onofré jbono...@apache.org http://blog.nanthrax.net Talend - http://wwx.talend.com - Reply message - From: "Andreas Pieber" To: Subject: Apache Karaf 2.3.0 very close Date: Mon, Oct 8, 2012 9:17 am Hey, On Mon, Oct 8, 2012 at 7:46 AM, Jean-Baptiste Onofré wrote: @Andreas, could you take a look on KARAF-1878 and KARAF-1752 (assigned to you) ? If you are busy today, I think we can postpone to 2.3.1. I wanted to keep KARAF-1878 opened for review till tonight; I'll apply afterwards. I'll also apply KARAF-1752 then. Kind regards, Andreas Thanks all guys, Regards JB -- Jean-Baptiste Onofré jbono...@apache.org http://blog.nanthrax.net Talend - http://www.talend.com -- Claus Ibsen - Red Hat, Inc. FuseSource is now part of Red Hat Email: cib...@redhat.com Web: http://fusesource.com Twitter: davsclaus Blog: http://davsclaus.com Author of Camel in Action: http://www.manning.com/ibsen -- Jean-Baptiste Onofré jbono...@apache.org http://blog.nanthrax.net Talend - http://www.talend.com
Re: Apache Karaf 2.3.0 very close
Spring 3.1.x is planned for Karaf 3.0 (with Jetty 8). For 2.3.x, I'm OK to upgrade to Jetty 7.6.7, but not sure for Spring 3.1.x. I'm not against, but we should have update before, not at 24 hours from the release. Let me make a try on my local working copy. Regards JB On 10/08/2012 05:55 PM, Claus Ibsen wrote: On Mon, Oct 8, 2012 at 5:45 PM, Jamie G. wrote: Hi Claus, From the Karaf 2.3.0 pom file: 1.2.1 2.5.6.SEC03 3.0.7.RELEASE Crap I think you guys shoulder consider switching to the 3.1.2 release of Spring. As well Jetty 7.6.7, so people have the latest stable release of these 2 important pieces. Cheers, Jamie On Mon, Oct 8, 2012 at 1:09 PM, Claus Ibsen wrote: Hi What Spring version does Karaf 2.3.0 come with out of the box? 3.0.x or the newer 3.1.x ? On Mon, Oct 8, 2012 at 10:53 AM, Jamie G. wrote: I'm always ready! Cheers, Jamie On Mon, Oct 8, 2012 at 5:08 AM, j...@nanthrax.net wrote: Great, thanks a lot ! -- Jean-Baptiste Onofré jbono...@apache.org http://blog.nanthrax.net Talend - http://wwx.talend.com - Reply message - From: "Andreas Pieber" To: Subject: Apache Karaf 2.3.0 very close Date: Mon, Oct 8, 2012 9:17 am Hey, On Mon, Oct 8, 2012 at 7:46 AM, Jean-Baptiste Onofré wrote: @Andreas, could you take a look on KARAF-1878 and KARAF-1752 (assigned to you) ? If you are busy today, I think we can postpone to 2.3.1. I wanted to keep KARAF-1878 opened for review till tonight; I'll apply afterwards. I'll also apply KARAF-1752 then. Kind regards, Andreas Thanks all guys, Regards JB -- Jean-Baptiste Onofré jbono...@apache.org http://blog.nanthrax.net Talend - http://www.talend.com -- Claus Ibsen - Red Hat, Inc. FuseSource is now part of Red Hat Email: cib...@redhat.com Web: http://fusesource.com Twitter: davsclaus Blog: http://davsclaus.com Author of Camel in Action: http://www.manning.com/ibsen -- Jean-Baptiste Onofré jbono...@apache.org http://blog.nanthrax.net Talend - http://www.talend.com
Re: Apache Karaf 2.3.0 very close
On Mon, Oct 8, 2012 at 5:45 PM, Jamie G. wrote: > Hi Claus, > > From the Karaf 2.3.0 pom file: > 1.2.1 > 2.5.6.SEC03 > 3.0.7.RELEASE > Crap I think you guys shoulder consider switching to the 3.1.2 release of Spring. As well Jetty 7.6.7, so people have the latest stable release of these 2 important pieces. > Cheers, > Jamie > > On Mon, Oct 8, 2012 at 1:09 PM, Claus Ibsen wrote: >> Hi >> >> What Spring version does Karaf 2.3.0 come with out of the box? 3.0.x >> or the newer 3.1.x ? >> >> On Mon, Oct 8, 2012 at 10:53 AM, Jamie G. wrote: >>> I'm always ready! >>> >>> Cheers, >>> Jamie >>> >>> On Mon, Oct 8, 2012 at 5:08 AM, j...@nanthrax.net wrote: >>>> Great, thanks a lot ! >>>> >>>> -- >>>> Jean-Baptiste Onofré >>>> jbono...@apache.org >>>> http://blog.nanthrax.net >>>> Talend - http://wwx.talend.com >>>> >>>> - Reply message - >>>> From: "Andreas Pieber" >>>> To: >>>> Subject: Apache Karaf 2.3.0 very close >>>> Date: Mon, Oct 8, 2012 9:17 am >>>> >>>> >>>> Hey, >>>> >>>> On Mon, Oct 8, 2012 at 7:46 AM, Jean-Baptiste Onofré >>>> wrote: >>>>> @Andreas, could you take a look on KARAF-1878 and KARAF-1752 (assigned to >>>>> you) ? If you are busy today, I think we can postpone to 2.3.1. >>>> >>>> I wanted to keep KARAF-1878 opened for review till tonight; I'll apply >>>> afterwards. I'll also apply KARAF-1752 then. >>>> >>>> Kind regards, >>>> Andreas >>>> >>>>> >>>>> Thanks all guys, >>>>> Regards >>>>> JB >>>>> -- >>>>> Jean-Baptiste Onofré >>>>> jbono...@apache.org >>>>> http://blog.nanthrax.net >>>>> Talend - http://www.talend.com >> >> >> >> -- >> Claus Ibsen >> - >> Red Hat, Inc. >> FuseSource is now part of Red Hat >> Email: cib...@redhat.com >> Web: http://fusesource.com >> Twitter: davsclaus >> Blog: http://davsclaus.com >> Author of Camel in Action: http://www.manning.com/ibsen -- Claus Ibsen - Red Hat, Inc. FuseSource is now part of Red Hat Email: cib...@redhat.com Web: http://fusesource.com Twitter: davsclaus Blog: http://davsclaus.com Author of Camel in Action: http://www.manning.com/ibsen
Re: Apache Karaf 2.3.0 very close
Hi Claus, >From the Karaf 2.3.0 pom file: 1.2.1 2.5.6.SEC03 3.0.7.RELEASE Cheers, Jamie On Mon, Oct 8, 2012 at 1:09 PM, Claus Ibsen wrote: > Hi > > What Spring version does Karaf 2.3.0 come with out of the box? 3.0.x > or the newer 3.1.x ? > > On Mon, Oct 8, 2012 at 10:53 AM, Jamie G. wrote: >> I'm always ready! >> >> Cheers, >> Jamie >> >> On Mon, Oct 8, 2012 at 5:08 AM, j...@nanthrax.net wrote: >>> Great, thanks a lot ! >>> >>> -- >>> Jean-Baptiste Onofré >>> jbono...@apache.org >>> http://blog.nanthrax.net >>> Talend - http://wwx.talend.com >>> >>> - Reply message - >>> From: "Andreas Pieber" >>> To: >>> Subject: Apache Karaf 2.3.0 very close >>> Date: Mon, Oct 8, 2012 9:17 am >>> >>> >>> Hey, >>> >>> On Mon, Oct 8, 2012 at 7:46 AM, Jean-Baptiste Onofré >>> wrote: >>>> @Andreas, could you take a look on KARAF-1878 and KARAF-1752 (assigned to >>>> you) ? If you are busy today, I think we can postpone to 2.3.1. >>> >>> I wanted to keep KARAF-1878 opened for review till tonight; I'll apply >>> afterwards. I'll also apply KARAF-1752 then. >>> >>> Kind regards, >>> Andreas >>> >>>> >>>> Thanks all guys, >>>> Regards >>>> JB >>>> -- >>>> Jean-Baptiste Onofré >>>> jbono...@apache.org >>>> http://blog.nanthrax.net >>>> Talend - http://www.talend.com > > > > -- > Claus Ibsen > - > Red Hat, Inc. > FuseSource is now part of Red Hat > Email: cib...@redhat.com > Web: http://fusesource.com > Twitter: davsclaus > Blog: http://davsclaus.com > Author of Camel in Action: http://www.manning.com/ibsen
Re: Apache Karaf 2.3.0 very close
Hi What Spring version does Karaf 2.3.0 come with out of the box? 3.0.x or the newer 3.1.x ? On Mon, Oct 8, 2012 at 10:53 AM, Jamie G. wrote: > I'm always ready! > > Cheers, > Jamie > > On Mon, Oct 8, 2012 at 5:08 AM, j...@nanthrax.net wrote: >> Great, thanks a lot ! >> >> -- >> Jean-Baptiste Onofré >> jbono...@apache.org >> http://blog.nanthrax.net >> Talend - http://wwx.talend.com >> >> ----- Reply message - >> From: "Andreas Pieber" >> To: >> Subject: Apache Karaf 2.3.0 very close >> Date: Mon, Oct 8, 2012 9:17 am >> >> >> Hey, >> >> On Mon, Oct 8, 2012 at 7:46 AM, Jean-Baptiste Onofré >> wrote: >>> @Andreas, could you take a look on KARAF-1878 and KARAF-1752 (assigned to >>> you) ? If you are busy today, I think we can postpone to 2.3.1. >> >> I wanted to keep KARAF-1878 opened for review till tonight; I'll apply >> afterwards. I'll also apply KARAF-1752 then. >> >> Kind regards, >> Andreas >> >>> >>> Thanks all guys, >>> Regards >>> JB >>> -- >>> Jean-Baptiste Onofré >>> jbono...@apache.org >>> http://blog.nanthrax.net >>> Talend - http://www.talend.com -- Claus Ibsen - Red Hat, Inc. FuseSource is now part of Red Hat Email: cib...@redhat.com Web: http://fusesource.com Twitter: davsclaus Blog: http://davsclaus.com Author of Camel in Action: http://www.manning.com/ibsen
Re: Apache Karaf 2.3.0 very close
I'm always ready! Cheers, Jamie On Mon, Oct 8, 2012 at 5:08 AM, j...@nanthrax.net wrote: > Great, thanks a lot ! > > -- > Jean-Baptiste Onofré > jbono...@apache.org > http://blog.nanthrax.net > Talend - http://wwx.talend.com > > - Reply message - > From: "Andreas Pieber" > To: > Subject: Apache Karaf 2.3.0 very close > Date: Mon, Oct 8, 2012 9:17 am > > > Hey, > > On Mon, Oct 8, 2012 at 7:46 AM, Jean-Baptiste Onofré > wrote: >> @Andreas, could you take a look on KARAF-1878 and KARAF-1752 (assigned to >> you) ? If you are busy today, I think we can postpone to 2.3.1. > > I wanted to keep KARAF-1878 opened for review till tonight; I'll apply > afterwards. I'll also apply KARAF-1752 then. > > Kind regards, > Andreas > >> >> Thanks all guys, >> Regards >> JB >> -- >> Jean-Baptiste Onofré >> jbono...@apache.org >> http://blog.nanthrax.net >> Talend - http://www.talend.com
Re: Apache Karaf 2.3.0 very close
Great, thanks a lot ! -- Jean-Baptiste Onofré jbono...@apache.org http://blog.nanthrax.net Talend - http://wwx.talend.com - Reply message - From: "Andreas Pieber" To: Subject: Apache Karaf 2.3.0 very close Date: Mon, Oct 8, 2012 9:17 am Hey, On Mon, Oct 8, 2012 at 7:46 AM, Jean-Baptiste Onofré wrote: > @Andreas, could you take a look on KARAF-1878 and KARAF-1752 (assigned to > you) ? If you are busy today, I think we can postpone to 2.3.1. I wanted to keep KARAF-1878 opened for review till tonight; I'll apply afterwards. I'll also apply KARAF-1752 then. Kind regards, Andreas > > Thanks all guys, > Regards > JB > -- > Jean-Baptiste Onofré > jbono...@apache.org > http://blog.nanthrax.net > Talend - http://www.talend.com
Re: Apache Karaf 2.3.0 very close
Hey, On Mon, Oct 8, 2012 at 7:46 AM, Jean-Baptiste Onofré wrote: > @Andreas, could you take a look on KARAF-1878 and KARAF-1752 (assigned to > you) ? If you are busy today, I think we can postpone to 2.3.1. I wanted to keep KARAF-1878 opened for review till tonight; I'll apply afterwards. I'll also apply KARAF-1752 then. Kind regards, Andreas > > Thanks all guys, > Regards > JB > -- > Jean-Baptiste Onofré > jbono...@apache.org > http://blog.nanthrax.net > Talend - http://www.talend.com
Re: Apache Karaf 2.3.0 very close
Hi Guillaume, No worries, we can wait for the end of Mina 2.0.7 vote and upgrade in Karaf. I gonna create the Jira about that (in order to avoid to forget it ;)). Regards JB On 10/08/2012 08:44 AM, Guillaume Nodet wrote: I hate to say this, but I wonder if it would be worthwhile to wait an additional 24 hours for a mina 2.0.7 release. Mina 2.0.5 broke compatibility and that's the one we're on now, which means some applications may just break if they're using an important method which has been accidentally deleted. Mina 2.0.6 has been released last week but contains an important regression. Mina 2.0.7 is under vote. On Mon, Oct 8, 2012 at 7:46 AM, Jean-Baptiste Onofré wrote: Hi all, We are now very close to the Karaf 2.3.0 release. We have 5 Jira still opened. I'm working on KARAF-1853 and KARAF-1354, and also on the itests on different platforms. @Andreas, could you take a look on KARAF-1878 and KARAF-1752 (assigned to you) ? If you are busy today, I think we can postpone to 2.3.1. @Jamie, I think we will be able to cut off Karaf 2.3.0 release tonight (GMT+1 time). Are you available for the release ? Thanks all guys, Regards JB -- Jean-Baptiste Onofré jbono...@apache.org http://blog.nanthrax.net Talend - http://www.talend.com -- Jean-Baptiste Onofré jbono...@apache.org http://blog.nanthrax.net Talend - http://www.talend.com
Re: Apache Karaf 2.3.0 very close
I hate to say this, but I wonder if it would be worthwhile to wait an additional 24 hours for a mina 2.0.7 release. Mina 2.0.5 broke compatibility and that's the one we're on now, which means some applications may just break if they're using an important method which has been accidentally deleted. Mina 2.0.6 has been released last week but contains an important regression. Mina 2.0.7 is under vote. On Mon, Oct 8, 2012 at 7:46 AM, Jean-Baptiste Onofré wrote: > Hi all, > > We are now very close to the Karaf 2.3.0 release. > > We have 5 Jira still opened. > > I'm working on KARAF-1853 and KARAF-1354, and also on the itests on > different platforms. > > @Andreas, could you take a look on KARAF-1878 and KARAF-1752 (assigned to > you) ? If you are busy today, I think we can postpone to 2.3.1. > > @Jamie, I think we will be able to cut off Karaf 2.3.0 release tonight > (GMT+1 time). Are you available for the release ? > > Thanks all guys, > Regards > JB > -- > Jean-Baptiste Onofré > jbono...@apache.org > http://blog.nanthrax.net > Talend - http://www.talend.com > -- Guillaume Nodet Blog: http://gnodet.blogspot.com/ FuseSource, Integration everywhere http://fusesource.com
Apache Karaf 2.3.0 very close
Hi all, We are now very close to the Karaf 2.3.0 release. We have 5 Jira still opened. I'm working on KARAF-1853 and KARAF-1354, and also on the itests on different platforms. @Andreas, could you take a look on KARAF-1878 and KARAF-1752 (assigned to you) ? If you are busy today, I think we can postpone to 2.3.1. @Jamie, I think we will be able to cut off Karaf 2.3.0 release tonight (GMT+1 time). Are you available for the release ? Thanks all guys, Regards JB -- Jean-Baptiste Onofré jbono...@apache.org http://blog.nanthrax.net Talend - http://www.talend.com
