Hi Upgrade to QuickFIX/J 1.5.2 is already done (CAMEL-5334). As well the camel-quickfix module is now enabled again on the Jenkins (Camel.trunk.fulltest.java7).
I did test both on OS X as well as WIN (JDK 6 & JDK 7). So let's see how it will go through the next build... Babak Claus Ibsen-2 wrote > > On Sat, Jun 2, 2012 at 10:17 PM, Babak Vahdat > <babak.vahdat@> wrote: >> The Java 7 support is not completely done yet as camel-quickfix is still >> the >> last missing piece of the task (currently disabled on the CI-Server). I >> did >> play around with upgrading to quickfixj 1.5.2 which first had some >> compilation error as well as unit-test failures (NPE) which I easily >> could >> fix locally. I'm just waiting for the bundle of it: >> >> https://issues.apache.org/jira/browse/SMX4-1153 >> > > So does quickfix 1.5.2 work with Java 7? > > Regardless of what its not a showstopper for the Camel 2.10 release. > We can add to known issues that camel-quickfix is known to not work > with Java7 due QuickFix itself. > > The release will be built using java 6, and thus the camel-quickfix > component will be included. > >> Babak >> >> >> Claus Ibsen-2 wrote >>> >>> Hi >>> >>> So the Java 7 support is now done. >>> And when CXF 2.6.1 is out, we should be in a shape for a release. >>> >>> I have created a JIRA version 2.11, and moved some tickets from 2.10 to >>> that. >>> As we should focus on closing the last bugs, minor improvements etc. >>> And keep eye on the CI servers to have a good build. >>> And test the examples. I think the twitter example is broken. >>> >>> Anything in particular you would like in 2.10, that are not yet done? >>> >>> >>> >>> On Tue, May 29, 2012 at 3:37 PM, Daniel Kulp <dan@> wrote: >>>> On Monday, May 28, 2012 06:17:27 PM Christian Müller wrote: >>>>> Camel 2.9.0 is now out since almost 5 month. In the next days, I will >>>>> have >>>>> more often an eye on Jenkis to see whether we have issues we have to >>>>> fix. >>>>> I will support Claus for the outstanding Java 7 issue. >>>>> If everything run's fine, we should start the release procedure in >>>>> this >>>>> or >>>>> next week. Do we already have release manager for this release? >>>> >>>> We'll need/want to wait for CXF 2.6.1 which I hope to build later >>>> tonight >>>> or >>>> tomorrow. >>>> >>>> >>>>> Afterwards we should roll out Camel 2.8.7., our last official 2.8. >>>>> release. I could do this, if no one else want do it. >>>> >>>> We'll also need/want to wait for 2.5.4 for a similar reason. I'm also >>>> a >>>> bit uncomfortable saying "last official". 2.8.0 was released last >>>> July >>>> so >>>> I would expect about one more before a full year of patches is up. >>>> >>>> >>>> >>>> -- >>>> Daniel Kulp >>>> dan@ >>>> http://dankulp.com/blog >>>> >>> >>> >>> >>> -- >>> Claus Ibsen >>> ----------------- >>> FuseSource >>> Email: cibsen@ >>> Web: http://fusesource.com >>> Twitter: davsclaus, fusenews >>> Blog: http://davsclaus.com >>> Author of Camel in Action: http://www.manning.com/ibsen >>> >> >> >> -- >> View this message in context: >> http://camel.465427.n5.nabble.com/DISCUSS-Apache-Camel-2-10-release-tp5691194p5713866.html >> Sent from the Camel Development mailing list archive at Nabble.com. > > > > -- > Claus Ibsen > ----------------- > FuseSource > Email: cibsen@ > Web: http://fusesource.com > Twitter: davsclaus, fusenews > Blog: http://davsclaus.com > Author of Camel in Action: http://www.manning.com/ibsen > -- View this message in context: http://camel.465427.n5.nabble.com/DISCUSS-Apache-Camel-2-10-release-tp5691194p5714066.html Sent from the Camel Development mailing list archive at Nabble.com.
