Hi Okay Camel 2.6 seems good now. Just fixed a few tests failures reported on CI servers, often due they are much slower than our local fast laptops.
CXF 2.3.2 is about to hit the streets so we should be good to go. So please refrain from committing to trunk, unless its a CI unit test fix :). New features or improvements should be postponed for Camel 2.7. Lets keep the activity on the trunk low so the CI servers have good chance to battle test it. Willem will commit the upgrade to CXF 2.3.2 which in fact may already be in central maven repo. On Tue, Jan 18, 2011 at 1:07 PM, Claus Ibsen <claus.ib...@gmail.com> wrote: > Hi > > I have created a ticket to upgrade to CXF 2.3.2 > https://issues.apache.org/jira/browse/CAMEL-3553 > > The CXF vote is in progress > http://cxf.547215.n5.nabble.com/VOTE-Apache-CXF-2-3-2-td3345633.html > > And the Camel source code trunk is testing against a 2.3.2-SNAPSHOT. > So we use that to catch any early issues. > > Better would have been to add the staging repo for the 2.3.2 and use that :) > > > We should focus on fixing any last minute bugs and ensures the release > has successful tests. > https://hudson.apache.org/hudson/job/Camel.trunk.fulltest/ > > > > > > -- > Claus Ibsen > ----------------- > FuseSource > Email: cib...@fusesource.com > Web: http://fusesource.com > Twitter: davsclaus > Blog: http://davsclaus.blogspot.com/ > Author of Camel in Action: http://www.manning.com/ibsen/ > -- Claus Ibsen ----------------- FuseSource Email: cib...@fusesource.com Web: http://fusesource.com Twitter: davsclaus Blog: http://davsclaus.blogspot.com/ Author of Camel in Action: http://www.manning.com/ibsen/
