Return-Path: X-Original-To: apmail-camel-dev-archive@www.apache.org Delivered-To: apmail-camel-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 8D616C1BE for ; Tue, 22 May 2012 13:19:18 +0000 (UTC) Received: (qmail 34404 invoked by uid 500); 22 May 2012 13:19:18 -0000 Delivered-To: apmail-camel-dev-archive@camel.apache.org Received: (qmail 34379 invoked by uid 500); 22 May 2012 13:19:18 -0000 Mailing-List: contact dev-help@camel.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@camel.apache.org Delivered-To: mailing list dev@camel.apache.org Received: (qmail 34368 invoked by uid 99); 22 May 2012 13:19:18 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 22 May 2012 13:19:18 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of claus.ibsen@gmail.com designates 209.85.217.173 as permitted sender) Received: from [209.85.217.173] (HELO mail-lb0-f173.google.com) (209.85.217.173) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 22 May 2012 13:19:14 +0000 Received: by lbok6 with SMTP id k6so5462591lbo.32 for ; Tue, 22 May 2012 06:18:52 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type:content-transfer-encoding; bh=WgohEhYpiDeQjneTTcjs4M4IWWmhaBQWmJklwE0ZLa0=; b=trZMkexQjtlgkXdWHWGf8gYHaj9IAV7YzpCKNH2FNdoJNfmVwrdb/8ZVB/pSohIyjn jGB/L9IM9AwjY0TUihjpB0p6t23bM8btCcQVp0BBfaAD7n9GUwKFbb00eddLKOPbOjt0 KtnO82+8lzNYzIHHdgwInzOIVQXlOEKY9Rjis2TDt0SveWHBvWa/GMR+exM335wDjNoy A2GBsZXYx0gkrYTDFTwXpwXheaDUa0IaG+Eh5RA4ttuBBroz+13rpsPMQKgyKpFJ9YUi qCml+wUfeCO/jJ8HiDxk93vZb/e/geA1Ewl3XrxoxVi8AJ4DzcTAdLSKBbkkyKeTX5O6 Xc/w== Received: by 10.112.42.66 with SMTP id m2mr2621566lbl.46.1337692732451; Tue, 22 May 2012 06:18:52 -0700 (PDT) MIME-Version: 1.0 Received: by 10.112.146.7 with HTTP; Tue, 22 May 2012 06:18:32 -0700 (PDT) In-Reply-To: References: <2795730.KAzWmP729h@dilbert.dankulp.com> <4130561.7fJQf7tg9N@dilbert.dankulp.com> From: Claus Ibsen Date: Tue, 22 May 2012 15:18:32 +0200 Message-ID: Subject: Re: [DISCUSS] - Apache Camel 2.10 release To: dev@camel.apache.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Virus-Checked: Checked by ClamAV on apache.org Hi Just a heads up. I have fixed the hdfs and zookeeper on windows java 7. I could not reproduce the failure on camel-sql. And currently testing the osgi ones, they take a long time as usual. Hope Willem get those tests upgraded to Pax-Exam 2.x soon. On Tue, May 22, 2012 at 11:34 AM, Claus Ibsen wrote= : > Hi > > I am currently working on polishing and fixing the tests so they work > on Java 7 on my Windows box. > Its looking really good, so far there is a few errors in the > - camel-hdfs > - camel-sql > - camel-zookeeper > - camel-itest-osgi > > I will work my way to see if these tests can be fixed along the way. > > > On Wed, May 9, 2012 at 1:10 PM, Claus Ibsen wrote= : >> Just a heads-up that Camel 2.10 now requires Maven 3.0.2 or better to >> build from source. >> We put out note in the 2.9 release notes that we would drop Maven 2.x su= pport. >> >> Also I upgrade the maven bundle plugin to 2.3.7, so keep an eye out if >> that plugin makes some mistakes. >> It has done that in the past. >> >> >> >> On Wed, May 9, 2012 at 11:08 AM, Christian M=FCller >> wrote: >>> Thanks Dan, thanks Claus, >>> >>> great work. I got a compile failure in camel-quickfix. Will have a look= on >>> it later... >>> >>> Best, >>> Christian >>> >>> On Wed, May 9, 2012 at 10:53 AM, Claus Ibsen wr= ote: >>> >>>> On Tue, May 8, 2012 at 9:02 PM, Daniel Kulp wrote: >>>> > >>>> > The latest Jenkins build definitely looks a TON better: >>>> > >>>> > >>>> > https://builds.apache.org/job/Camel.trunk.fulltest.java7/82/ >>>> > >>>> >>>> Great work. Nice to see it down to a manageable size. >>>> >>>> At first glance many of those test failures is due to port number in u= se. >>>> A bit odd as some of these components ought to use the free port finde= r. >>>> >>>> >>>> > :-) >>>> > >>>> > Most of the test failures are with SSL related tests. =A0They pass o= n my >>>> > machine fine so it's a bit concerning to me. =A0However, I always ha= ve the >>>> > unlimited strength crypto things installed due to my work on the >>>> ws-security >>>> > things and wss4j and such. =A0I'm not sure it that may be part of it= or not >>>> > yet. =A0 I'd have to setup a separate JDK setup to test that. =A0Can= someone >>>> > with a non-JCE JDK7 setup check some of those tests and see if that = may >>>> be >>>> > the issue? >>>> > >>>> >>>> If I find some cycles I will try installing a vanilla JDK7 on my xp >>>> box (this wont have the unlimted strengh crypto) >>>> And give it a test run. >>>> >>>> >>>> >>>> > >>>> > >>>> > Dan >>>> > >>>> > >>>> > >>>> > >>>> > On Tuesday, May 08, 2012 01:04:28 PM Daniel Kulp wrote: >>>> >> On Tuesday, May 08, 2012 05:00:50 PM Christian M=FCller wrote: >>>> >> > For private reasons I cannot work on Camel 2.10.0 as I want. I wi= ll do >>>> >> > my >>>> >> > best to resolve my two outstanding issues in the next week. If th= is is >>>> >> > not possible, it's no problem to postpone it to Camel 2.10.1. >>>> >> > >>>> >> > The only one issue which is not resolved at the moment and I work= ed on >>>> >> > (it's not assigned to anybody at present) and which should be res= olved >>>> >> > in >>>> >> > Camel 2.10.0 in my opinion is: >>>> >> > CAMEL-4955: Camel should run in a Java 7 environment >>>> >> > May be we have a voluntary which could support me? The Jenkins bu= ild >>>> >> > results are here [1]. >>>> >> >>>> >> I've pretty much picked this up for you. =A0 I'm at a point now whe= re all >>>> of >>>> >> Camel *BUILDS* other that quickfix. =A0 All of the component/* unit= tests >>>> >> now pass as well (although some randomly fail, but that's no differ= ent >>>> >> than with J6). =A0 I'm getting a bunch of failures in the itests. = =A0 That's >>>> >> next to look at. >>>> >> >>>> >> Dan >>>> >> >>>> >> > If I have a few hours left, I will also have a look on some >>>> >> > other/smaller >>>> >> > enhancements which could go into Camel 2.10.0. >>>> >> > >>>> >> > [1] >>>> >> > >>>> https://builds.apache.org/view/A-F/view/Camel/job/Camel.trunk.fulltest= .j >>>> >> > av a7/ >>>> >> > >>>> >> > Best, >>>> >> > Christian >>>> >> > >>>> >> > On Mon, May 7, 2012 at 4:27 PM, Claus Ibsen >>>> > wrote: >>>> >> > > Hi >>>> >> > > >>>> >> > > I think its time we start close down on a Camel 2.10 release. T= he >>>> >> > > 2.9.0 release was on January 1sy 2012, so its been 4.5 months s= ince >>>> >> > > that release. Yes in between there has been 2 patch releases, e= g >>>> >> > > 2.9.1, and 2.9.2 etc. >>>> >> > > >>>> >> > > There is some new components added in Camel 2.10, and most of t= hem >>>> now >>>> >> > > have adequate documentation. >>>> >> > > But I think a few is missing. The camel-leveldb is essentially = a >>>> copy >>>> >> > > of the camel-hawtdb component, so the documentation is fairly e= asy >>>> as >>>> >> > > it would be a copy, and then some adjustments. The camel-leveld= b is >>>> >> > > not yet OSGi compliant. We may need to push that for Camel 2.11= or a >>>> >> > > patch release of 2.10. >>>> >> > > >>>> >> > > When the AMQ 5.6.0 release is out, we can bump that in the came= l-jms >>>> >> > > testing, to ensure we test against that release. >>>> >> > > >>>> >> > > In the JIRA tracker there is 70+ unresolved tickets scheduled f= or >>>> 2.10 >>>> >> > > >>>> >> > > >>>> https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=3Dtrue= &j >>>> >> > > ql >>>> >> > > >>>> Query=3Dproject+%3D+CAMEL+AND+fixVersion+%3D+%222.10.0%22+AND+resoluti= on >>>> >> > > +% >>>> >> > > 3D+Unresolved >>>> >> > > >>>> >> > > We may be able to push some for 2.10.1, or 2.11. >>>> >> > > I will create a 2.10.1 version so people can move tickets to th= is >>>> >> > > version. >>>> >> > > >>>> >> > > >>>> >> > > -- >>>> >> > > Claus Ibsen >>>> >> > > ----------------- >>>> >> > > CamelOne 2012 Conference, May 15-16, 2012: http://camelone.com >>>> >> > > FuseSource >>>> >> > > Email: cibsen@fusesource.com >>>> >> > > Web: http://fusesource.com >>>> >> > > Twitter: davsclaus, fusenews >>>> >> > > Blog: http://davsclaus.blogspot.com/ >>>> >> > > Author of Camel in Action: http://www.manning.com/ibsen/ >>>> > -- >>>> > Daniel Kulp >>>> > dkulp@apache.org - http://dankulp.com/blog >>>> > Talend Community Coder - http://coders.talend.com >>>> > >>>> >>>> >>>> >>>> -- >>>> Claus Ibsen >>>> ----------------- >>>> CamelOne 2012 Conference, May 15-16, 2012: http://camelone.com >>>> FuseSource >>>> Email: cibsen@fusesource.com >>>> Web: http://fusesource.com >>>> Twitter: davsclaus, fusenews >>>> Blog: http://davsclaus.blogspot.com/ >>>> Author of Camel in Action: http://www.manning.com/ibsen/ >>>> >> >> >> >> -- >> Claus Ibsen >> ----------------- >> CamelOne 2012 Conference, May 15-16, 2012: http://camelone.com >> FuseSource >> Email: cibsen@fusesource.com >> Web: http://fusesource.com >> Twitter: davsclaus, fusenews >> Blog: http://davsclaus.blogspot.com/ >> Author of Camel in Action: http://www.manning.com/ibsen/ > > > > -- > Claus Ibsen > ----------------- > CamelOne 2012 Conference, May 15-16, 2012: http://camelone.com > FuseSource > Email: cibsen@fusesource.com > Web: http://fusesource.com > Twitter: davsclaus, fusenews > Blog: http://davsclaus.blogspot.com/ > Author of Camel in Action: http://www.manning.com/ibsen/ --=20 Claus Ibsen ----------------- CamelOne 2012 Conference, May 15-16, 2012: http://camelone.com FuseSource Email: cibsen@fusesource.com Web: http://fusesource.com Twitter: davsclaus, fusenews Blog: http://davsclaus.blogspot.com/ Author of Camel in Action: http://www.manning.com/ibsen/