On Monday 17 January 2011 10:01:32 am Claus Ibsen wrote: > On Mon, Jan 17, 2011 at 3:55 PM, Daniel Kulp <dk...@apache.org> wrote: > > On Monday 17 January 2011 9:31:33 am Hadrian Zbarcea wrote: > >> Camel 2.6 is almost ready for a release. The last hudson test [1] only > >> had 4 failures in camel-scala (looks like the problem wasn't fully > >> resolved by Willem, and the problem still exists in the current build > >> [2]). It looks like everything else is really stable and I'd suggest > >> not committing patches that may impact stability until the release is > >> voted. I'll look at the scala issue too and that should be fixed today, > >> so tomorrow we should be ready for the builds. > >> > >> From what I see, SMX is looking forward to using camel 2.6 with cxf > >> 2.3.2 which is being built now. Should we wait another 2-3 days and > >> release camel-2.6.0 with cxf upgraded to 2.3.2? I saw Willem, Gert, > >> Johan and JB involved in that discussion. Guys, since you understand > >> the options and implications best, what's your suggestion? > > > > Well, I really think if anyone that will be using Camel and CXF together > > in an OSGi environment is really going to need the OSGi related fixes in > > 2.3.2. There's just a bunch of things that won't work correctly in OSGi > > with 2.3.1. Thus, if Camel uses 2.3.1, anyone running in OSGi will > > likely need to override it anyway. I suggest waiting a couple days. > > People have been using Camel and CXF in OSGi environments for a > reasonable long time now.
With CXF 2.2.x, not 2.3.x. There is a difference and a couple regressions now fixed. :-) Dan > But great that the different projects is improved and works better in > the OSGi runtimes. > > I think it would make sense to wait for 2.3.2 if its a reasonable > simple upgrade. > > Would be nice if Willem Jiang could try upgrading to use CXF > 2.3.2-SNAPSHOT on the trunk code of Camel and run tests to see if > there is anything that "doesnt work as usual". > > > Dan > > > >> Hadrian > >> > >> [1] https://hudson.apache.org/hudson/job/Camel.trunk.fulltest/119/ > >> [2] > >> https://hudson.apache.org/hudson/job/Camel.trunk.fulltest/120/org.apache > >> .c amel$camel-scala/ > >> > >> On Jan 16, 2011, at 3:45 AM, Claus Ibsen wrote: > >> > Thanks Christian > >> > > >> > All tickets for Camel 2.6 has now been resolved. So lets give the CI > >> > servers some time to test it. > >> > If all is well early next week, then Hadrian can start cutting the > >> > release. > >> > > >> > Thanks for all the hard work on this release. Its another staggering > >> > 250+ tickets resolve release. > >> > And great contributions from the community. > >> > > >> > > >> > On Sun, Jan 16, 2011 at 9:37 AM, Christian Müller > >> > > >> > <christian.muel...@gmail.com> wrote: > >> >> I reverted the changes for > >> >> https://issues.apache.org/jira/browse/CAMEL-3311and closed this > >> >> issue. I will implement this feature in a better solution in > >> >> Camel 2.7 with > >> >> https://issues.apache.org/jira/browse/CAMEL-3515<https://issues.apach > >> >> e. org/jira/browse/CAMEL-3311> . > > > > -- > > Daniel Kulp > > dk...@apache.org > > http://dankulp.com/blog -- Daniel Kulp dk...@apache.org http://dankulp.com/blog
