[DISCUSS] - Apache Camel 2.10 release

[Claus Ibsen-2]

Hi

I think its time we start close down on a Camel 2.10 release. The
2.9.0 release was on January 1sy 2012, so its been 4.5 months since
that release. Yes in between there has been 2 patch releases, eg
2.9.1, and 2.9.2 etc.

There is some new components added in Camel 2.10, and most of them 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 easy as
it would be a copy, and then some adjustments. The camel-leveldb 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 camel-jms
testing, to ensure we test against that release.

In the JIRA tracker there is 70+ unresolved tickets scheduled for 2.10
https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&jqlQuery=project+%3D+CAMEL+AND+fixVersion+%3D+%222.10.0%22+AND+resolution+%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 this version.


--
Claus Ibsen
-----------------
CamelOne 2012 Conference, May 15-16, 2012: http://camelone.com
FuseSource
Email: [hidden email]
Web: http://fusesource.com
Twitter: davsclaus, fusenews
Blog: http://davsclaus.blogspot.com/
Author of Camel in Action: http://www.manning.com/ibsen/

[Christian Mueller]

For private reasons I cannot work on Camel 2.10.0 as I want. I will do my
best to resolve my two outstanding issues in the next week. If this 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 worked on
(it's not assigned to anybody at present) and which should be resolved 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 build
results are here [1].

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.java7/

Best,
Christian

On Mon, May 7, 2012 at 4:27 PM, Claus Ibsen <[hidden email]> wrote:

> Hi
>
> I think its time we start close down on a Camel 2.10 release. The
> 2.9.0 release was on January 1sy 2012, so its been 4.5 months since
> that release. Yes in between there has been 2 patch releases, eg
> 2.9.1, and 2.9.2 etc.
>
> There is some new components added in Camel 2.10, and most of them 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 easy as
> it would be a copy, and then some adjustments. The camel-leveldb 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 camel-jms
> testing, to ensure we test against that release.
>
> In the JIRA tracker there is 70+ unresolved tickets scheduled for 2.10
>
> https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&jqlQuery=project+%3D+CAMEL+AND+fixVersion+%3D+%222.10.0%22+AND+resolution+%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 this version.
>
>
> --
> Claus Ibsen
> -----------------
> CamelOne 2012 Conference, May 15-16, 2012: http://camelone.com
> FuseSource
> Email: [hidden email]
> Web: http://fusesource.com
> Twitter: davsclaus, fusenews
> Blog: http://davsclaus.blogspot.com/
> Author of Camel in Action: http://www.manning.com/ibsen/
>

[Christian Schneider]

Hi Claus,

I am currently working on making the camel commands compatible with
karaf 3. Would be great if we could get this into 2.10
https://issues.apache.org/jira/browse/KARAF-1451

In karaf it is the issue above. I will also create an issue in camel for
it. The change should be fairly small.

Christian

Am 07.05.2012 16:27, schrieb Claus Ibsen:

> Hi
>
> I think its time we start close down on a Camel 2.10 release. The
> 2.9.0 release was on January 1sy 2012, so its been 4.5 months since
> that release. Yes in between there has been 2 patch releases, eg
> 2.9.1, and 2.9.2 etc.
>
> There is some new components added in Camel 2.10, and most of them 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 easy as
> it would be a copy, and then some adjustments. The camel-leveldb 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 camel-jms
> testing, to ensure we test against that release.
>
> In the JIRA tracker there is 70+ unresolved tickets scheduled for 2.10
> https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&jqlQuery=project+%3D+CAMEL+AND+fixVersion+%3D+%222.10.0%22+AND+resolution+%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 this version.
>
>

--
Christian Schneider
http://www.liquid-reality.de

Open Source Architect
Talend Application Integration Division http://www.talend.com

[Jean-Baptiste Onofré]

Hi Christian,

I don't think it's blocker for Camel 2.10.

On my side, I will work on the RMI component improvements (not blocker
for 2.10 either).

Regards
JB

On 05/08/2012 06:23 PM, Christian Schneider wrote:

> Hi Claus,
>
> I am currently working on making the camel commands compatible with
> karaf 3. Would be great if we could get this into 2.10
> https://issues.apache.org/jira/browse/KARAF-1451
>
> In karaf it is the issue above. I will also create an issue in camel for
> it. The change should be fairly small.
>
> Christian
>
> Am 07.05.2012 16:27, schrieb Claus Ibsen:
>> Hi
>>
>> I think its time we start close down on a Camel 2.10 release. The
>> 2.9.0 release was on January 1sy 2012, so its been 4.5 months since
>> that release. Yes in between there has been 2 patch releases, eg
>> 2.9.1, and 2.9.2 etc.
>>
>> There is some new components added in Camel 2.10, and most of them 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 easy as
>> it would be a copy, and then some adjustments. The camel-leveldb 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 camel-jms
>> testing, to ensure we test against that release.
>>
>> In the JIRA tracker there is 70+ unresolved tickets scheduled for 2.10
>> https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&jqlQuery=project+%3D+CAMEL+AND+fixVersion+%3D+%222.10.0%22+AND+resolution+%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 this
>> version.
>>
>>
>
>

--
Jean-Baptiste Onofré
[hidden email]
http://blog.nanthrax.net
Talend - http://www.talend.com

On Tuesday, May 08, 2012 05:00:50 PM Christian Müller wrote:

> For private reasons I cannot work on Camel 2.10.0 as I want. I will do my
> best to resolve my two outstanding issues in the next week. If this 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 worked on
> (it's not assigned to anybody at present) and which should be resolved 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 build
> results are here [1].

I've pretty much picked this up for you.   I'm at a point now where all of
Camel *BUILDS* other that quickfix.   All of the component/* unit tests now
pass as well (although some randomly fail, but that's no different than with
J6).   I'm getting a bunch of failures in the itests.   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.jav
> a7/
>
> Best,
> Christian
>
> On Mon, May 7, 2012 at 4:27 PM, Claus Ibsen <[hidden email]> wrote:
> > Hi
> >
> > I think its time we start close down on a Camel 2.10 release. The
> > 2.9.0 release was on January 1sy 2012, so its been 4.5 months since
> > that release. Yes in between there has been 2 patch releases, eg
> > 2.9.1, and 2.9.2 etc.
> >
> > There is some new components added in Camel 2.10, and most of them 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 easy as
> > it would be a copy, and then some adjustments. The camel-leveldb 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 camel-jms
> > testing, to ensure we test against that release.
> >
> > In the JIRA tracker there is 70+ unresolved tickets scheduled for 2.10
> >
> > https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&jql
> > Query=project+%3D+CAMEL+AND+fixVersion+%3D+%222.10.0%22+AND+resolution+%
> > 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 this
> > version.
> >
> >
> > --
> > Claus Ibsen
> > -----------------
> > CamelOne 2012 Conference, May 15-16, 2012: http://camelone.com
> > FuseSource
> > Email: [hidden email]
> > Web: http://fusesource.com
> > Twitter: davsclaus, fusenews
> > Blog: http://davsclaus.blogspot.com/
> > Author of Camel in Action: http://www.manning.com/ibsen/

--
Daniel Kulp
[hidden email] - http://dankulp.com/blog
Talend Community Coder - http://coders.talend.com

The latest Jenkins build definitely looks a TON better:


https://builds.apache.org/job/Camel.trunk.fulltest.java7/82/

:-)

Most of the test failures are with SSL related tests.  They pass on my
machine fine so it's a bit concerning to me.  However, I always have the
unlimited strength crypto things installed due to my work on the ws-security
things and wss4j and such.  I'm not sure it that may be part of it or not
yet.   I'd have to setup a separate JDK setup to test that.  Can someone
with a non-JCE JDK7 setup check some of those tests and see if that may be
the issue?



Dan




On Tuesday, May 08, 2012 01:04:28 PM Daniel Kulp wrote:

> On Tuesday, May 08, 2012 05:00:50 PM Christian Müller wrote:
> > For private reasons I cannot work on Camel 2.10.0 as I want. I will do
> > my
> > best to resolve my two outstanding issues in the next week. If this 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 worked on
> > (it's not assigned to anybody at present) and which should be resolved
> > 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 build
> > results are here [1].
>
> I've pretty much picked this up for you.   I'm at a point now where all of
> Camel *BUILDS* other that quickfix.   All of the component/* unit tests
> now pass as well (although some randomly fail, but that's no different
> than with J6).   I'm getting a bunch of failures in the itests.   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 <[hidden email]>

wrote:

> > > Hi
> > >
> > > I think its time we start close down on a Camel 2.10 release. The
> > > 2.9.0 release was on January 1sy 2012, so its been 4.5 months since
> > > that release. Yes in between there has been 2 patch releases, eg
> > > 2.9.1, and 2.9.2 etc.
> > >
> > > There is some new components added in Camel 2.10, and most of them 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 easy as
> > > it would be a copy, and then some adjustments. The camel-leveldb 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 camel-jms
> > > testing, to ensure we test against that release.
> > >
> > > In the JIRA tracker there is 70+ unresolved tickets scheduled for 2.10
> > >
> > > https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&j
> > > ql
> > > Query=project+%3D+CAMEL+AND+fixVersion+%3D+%222.10.0%22+AND+resolution
> > > +%
> > > 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 this
> > > version.
> > >
> > >
> > > --
> > > Claus Ibsen
> > > -----------------
> > > CamelOne 2012 Conference, May 15-16, 2012: http://camelone.com
> > > FuseSource
> > > Email: [hidden email]
> > > Web: http://fusesource.com
> > > Twitter: davsclaus, fusenews
> > > Blog: http://davsclaus.blogspot.com/
> > > Author of Camel in Action: http://www.manning.com/ibsen/

--
Daniel Kulp
[hidden email] - http://dankulp.com/blog
Talend Community Coder - http://coders.talend.com

[Christian Schneider]

Already done.
https://issues.apache.org/jira/browse/CAMEL-5254

It is just the package import. I will also backport to 2.9.x.

Dan came up with another issue that we will have with karaf 3. As Aries
will be upgraded to 1.0 we will also have to check these imports. Not
sure if this will make it to 2.10.0 though.

Christian

Am 08.05.2012 18:58, schrieb Jean-Baptiste Onofré:

> Hi Christian,
>
> I don't think it's blocker for Camel 2.10.
>
> On my side, I will work on the RMI component improvements (not blocker
> for 2.10 either).
>
> Regards
> JB
>
> On 05/08/2012 06:23 PM, Christian Schneider wrote:
>> Hi Claus,
>>
>> I am currently working on making the camel commands compatible with
>> karaf 3. Would be great if we could get this into 2.10
>> https://issues.apache.org/jira/browse/KARAF-1451
>>
>> In karaf it is the issue above. I will also create an issue in camel for
>> it. The change should be fairly small.
>>
>> Christian
>>
>> Am 07.05.2012 16:27, schrieb Claus Ibsen:
>>> Hi
>>>
>>> I think its time we start close down on a Camel 2.10 release. The
>>> 2.9.0 release was on January 1sy 2012, so its been 4.5 months since
>>> that release. Yes in between there has been 2 patch releases, eg
>>> 2.9.1, and 2.9.2 etc.
>>>
>>> There is some new components added in Camel 2.10, and most of them 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 easy as
>>> it would be a copy, and then some adjustments. The camel-leveldb 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 camel-jms
>>> testing, to ensure we test against that release.
>>>
>>> In the JIRA tracker there is 70+ unresolved tickets scheduled for 2.10
>>> https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&jqlQuery=project+%3D+CAMEL+AND+fixVersion+%3D+%222.10.0%22+AND+resolution+%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 this
>>> version.
>>>
>>>
>>
>>
>

--
Christian Schneider
http://www.liquid-reality.de

Open Source Architect
Talend Application Integration Division http://www.talend.com

[Claus Ibsen-2]

On Tue, May 8, 2012 at 9:02 PM, Daniel Kulp <[hidden email]> 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 use.
A bit odd as some of these components ought to use the free port finder.

> :-)
>
> Most of the test failures are with SSL related tests.  They pass on my
> machine fine so it's a bit concerning to me.  However, I always have the
> unlimited strength crypto things installed due to my work on the ws-security
> things and wss4j and such.  I'm not sure it that may be part of it or not
> yet.   I'd have to setup a separate JDK setup to test that.  Can 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üller wrote:
>> > For private reasons I cannot work on Camel 2.10.0 as I want. I will do
>> > my
>> > best to resolve my two outstanding issues in the next week. If this 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 worked on
>> > (it's not assigned to anybody at present) and which should be resolved
>> > 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 build
>> > results are here [1].
>>
>> I've pretty much picked this up for you.   I'm at a point now where all of
>> Camel *BUILDS* other that quickfix.   All of the component/* unit tests
>> now pass as well (although some randomly fail, but that's no different
>> than with J6).   I'm getting a bunch of failures in the itests.   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 <[hidden email]>
> wrote:
>> > > Hi
>> > >
>> > > I think its time we start close down on a Camel 2.10 release. The
>> > > 2.9.0 release was on January 1sy 2012, so its been 4.5 months since
>> > > that release. Yes in between there has been 2 patch releases, eg
>> > > 2.9.1, and 2.9.2 etc.
>> > >
>> > > There is some new components added in Camel 2.10, and most of them 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 easy as
>> > > it would be a copy, and then some adjustments. The camel-leveldb 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 camel-jms
>> > > testing, to ensure we test against that release.
>> > >
>> > > In the JIRA tracker there is 70+ unresolved tickets scheduled for 2.10
>> > >
>> > > https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&j
>> > > ql
>> > > Query=project+%3D+CAMEL+AND+fixVersion+%3D+%222.10.0%22+AND+resolution
>> > > +%
>> > > 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 this
>> > > version.
>> > >
>> > >
>> > > --
>> > > Claus Ibsen
>> > > -----------------
>> > > CamelOne 2012 Conference, May 15-16, 2012: http://camelone.com
>> > > FuseSource
>> > > Email: [hidden email]
>> > > Web: http://fusesource.com
>> > > Twitter: davsclaus, fusenews
>> > > Blog: http://davsclaus.blogspot.com/
>> > > Author of Camel in Action: http://www.manning.com/ibsen/
> --
> Daniel Kulp
> [hidden email] - 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: [hidden email]
Web: http://fusesource.com
Twitter: davsclaus, fusenews
Blog: http://davsclaus.blogspot.com/
Author of Camel in Action: http://www.manning.com/ibsen/

[Christian Mueller]

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 <[hidden email]> wrote:

> On Tue, May 8, 2012 at 9:02 PM, Daniel Kulp <[hidden email]> 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 use.
> A bit odd as some of these components ought to use the free port finder.
>
>
> > :-)
> >
> > Most of the test failures are with SSL related tests.  They pass on my
> > machine fine so it's a bit concerning to me.  However, I always have the
> > unlimited strength crypto things installed due to my work on the
> ws-security
> > things and wss4j and such.  I'm not sure it that may be part of it or not
> > yet.   I'd have to setup a separate JDK setup to test that.  Can 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üller wrote:
> >> > For private reasons I cannot work on Camel 2.10.0 as I want. I will do
> >> > my
> >> > best to resolve my two outstanding issues in the next week. If this 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 worked on
> >> > (it's not assigned to anybody at present) and which should be resolved
> >> > 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 build
> >> > results are here [1].
> >>
> >> I've pretty much picked this up for you.   I'm at a point now where all
> of
> >> Camel *BUILDS* other that quickfix.   All of the component/* unit tests
> >> now pass as well (although some randomly fail, but that's no different
> >> than with J6).   I'm getting a bunch of failures in the itests.   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 <[hidden email]>
> > wrote:
> >> > > Hi
> >> > >
> >> > > I think its time we start close down on a Camel 2.10 release. The
> >> > > 2.9.0 release was on January 1sy 2012, so its been 4.5 months since
> >> > > that release. Yes in between there has been 2 patch releases, eg
> >> > > 2.9.1, and 2.9.2 etc.
> >> > >
> >> > > There is some new components added in Camel 2.10, and most of them
> 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 easy
> as
> >> > > it would be a copy, and then some adjustments. The camel-leveldb 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 camel-jms
> >> > > testing, to ensure we test against that release.
> >> > >
> >> > > In the JIRA tracker there is 70+ unresolved tickets scheduled for
> 2.10
> >> > >
> >> > >
> https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&j
> >> > > ql
> >> > >
> Query=project+%3D+CAMEL+AND+fixVersion+%3D+%222.10.0%22+AND+resolution
> >> > > +%
> >> > > 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 this
> >> > > version.
> >> > >
> >> > >
> >> > > --
> >> > > Claus Ibsen
> >> > > -----------------
> >> > > CamelOne 2012 Conference, May 15-16, 2012: http://camelone.com
> >> > > FuseSource
> >> > > Email: [hidden email]
> >> > > Web: http://fusesource.com
> >> > > Twitter: davsclaus, fusenews
> >> > > Blog: http://davsclaus.blogspot.com/
> >> > > Author of Camel in Action: http://www.manning.com/ibsen/
> > --
> > Daniel Kulp
> > [hidden email] - 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: [hidden email]
> Web: http://fusesource.com
> Twitter: davsclaus, fusenews
> Blog: http://davsclaus.blogspot.com/
> Author of Camel in Action: http://www.manning.com/ibsen/
>

[Claus Ibsen-2]

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 support.

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üller
<[hidden email]> 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 <[hidden email]> wrote:
>
>> On Tue, May 8, 2012 at 9:02 PM, Daniel Kulp <[hidden email]> 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 use.
>> A bit odd as some of these components ought to use the free port finder.
>>
>>
>> > :-)
>> >
>> > Most of the test failures are with SSL related tests.  They pass on my
>> > machine fine so it's a bit concerning to me.  However, I always have the
>> > unlimited strength crypto things installed due to my work on the
>> ws-security
>> > things and wss4j and such.  I'm not sure it that may be part of it or not
>> > yet.   I'd have to setup a separate JDK setup to test that.  Can 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üller wrote:
>> >> > For private reasons I cannot work on Camel 2.10.0 as I want. I will do
>> >> > my
>> >> > best to resolve my two outstanding issues in the next week. If this 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 worked on
>> >> > (it's not assigned to anybody at present) and which should be resolved
>> >> > 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 build
>> >> > results are here [1].
>> >>
>> >> I've pretty much picked this up for you.   I'm at a point now where all
>> of
>> >> Camel *BUILDS* other that quickfix.   All of the component/* unit tests
>> >> now pass as well (although some randomly fail, but that's no different
>> >> than with J6).   I'm getting a bunch of failures in the itests.   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 <[hidden email]>
>> > wrote:
>> >> > > Hi
>> >> > >
>> >> > > I think its time we start close down on a Camel 2.10 release. The
>> >> > > 2.9.0 release was on January 1sy 2012, so its been 4.5 months since
>> >> > > that release. Yes in between there has been 2 patch releases, eg
>> >> > > 2.9.1, and 2.9.2 etc.
>> >> > >
>> >> > > There is some new components added in Camel 2.10, and most of them
>> 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 easy
>> as
>> >> > > it would be a copy, and then some adjustments. The camel-leveldb 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 camel-jms
>> >> > > testing, to ensure we test against that release.
>> >> > >
>> >> > > In the JIRA tracker there is 70+ unresolved tickets scheduled for
>> 2.10
>> >> > >
>> >> > >
>> https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&j
>> >> > > ql
>> >> > >
>> Query=project+%3D+CAMEL+AND+fixVersion+%3D+%222.10.0%22+AND+resolution
>> >> > > +%
>> >> > > 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 this
>> >> > > version.
>> >> > >
>> >> > >
>> >> > > --
>> >> > > Claus Ibsen
>> >> > > -----------------
>> >> > > CamelOne 2012 Conference, May 15-16, 2012: http://camelone.com
>> >> > > FuseSource
>> >> > > Email: [hidden email]
>> >> > > Web: http://fusesource.com
>> >> > > Twitter: davsclaus, fusenews
>> >> > > Blog: http://davsclaus.blogspot.com/
>> >> > > Author of Camel in Action: http://www.manning.com/ibsen/
>> > --
>> > Daniel Kulp
>> > [hidden email] - 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: [hidden email]
>> 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: [hidden email]
Web: http://fusesource.com
Twitter: davsclaus, fusenews
Blog: http://davsclaus.blogspot.com/
Author of Camel in Action: http://www.manning.com/ibsen/

[Claus Ibsen-2]

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 <[hidden email]> 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 support.
>
> 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üller
> <[hidden email]> 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 <[hidden email]> wrote:
>>
>>> On Tue, May 8, 2012 at 9:02 PM, Daniel Kulp <[hidden email]> 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 use.
>>> A bit odd as some of these components ought to use the free port finder.
>>>
>>>
>>> > :-)
>>> >
>>> > Most of the test failures are with SSL related tests.  They pass on my
>>> > machine fine so it's a bit concerning to me.  However, I always have the
>>> > unlimited strength crypto things installed due to my work on the
>>> ws-security
>>> > things and wss4j and such.  I'm not sure it that may be part of it or not
>>> > yet.   I'd have to setup a separate JDK setup to test that.  Can 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üller wrote:
>>> >> > For private reasons I cannot work on Camel 2.10.0 as I want. I will do
>>> >> > my
>>> >> > best to resolve my two outstanding issues in the next week. If this 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 worked on
>>> >> > (it's not assigned to anybody at present) and which should be resolved
>>> >> > 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 build
>>> >> > results are here [1].
>>> >>
>>> >> I've pretty much picked this up for you.   I'm at a point now where all
>>> of
>>> >> Camel *BUILDS* other that quickfix.   All of the component/* unit tests
>>> >> now pass as well (although some randomly fail, but that's no different
>>> >> than with J6).   I'm getting a bunch of failures in the itests.   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 <[hidden email]>
>>> > wrote:
>>> >> > > Hi
>>> >> > >
>>> >> > > I think its time we start close down on a Camel 2.10 release. The
>>> >> > > 2.9.0 release was on January 1sy 2012, so its been 4.5 months since
>>> >> > > that release. Yes in between there has been 2 patch releases, eg
>>> >> > > 2.9.1, and 2.9.2 etc.
>>> >> > >
>>> >> > > There is some new components added in Camel 2.10, and most of them
>>> 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 easy
>>> as
>>> >> > > it would be a copy, and then some adjustments. The camel-leveldb 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 camel-jms
>>> >> > > testing, to ensure we test against that release.
>>> >> > >
>>> >> > > In the JIRA tracker there is 70+ unresolved tickets scheduled for
>>> 2.10
>>> >> > >
>>> >> > >
>>> https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&j
>>> >> > > ql
>>> >> > >
>>> Query=project+%3D+CAMEL+AND+fixVersion+%3D+%222.10.0%22+AND+resolution
>>> >> > > +%
>>> >> > > 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 this
>>> >> > > version.
>>> >> > >
>>> >> > >
>>> >> > > --
>>> >> > > Claus Ibsen
>>> >> > > -----------------
>>> >> > > CamelOne 2012 Conference, May 15-16, 2012: http://camelone.com
>>> >> > > FuseSource
>>> >> > > Email: [hidden email]
>>> >> > > Web: http://fusesource.com
>>> >> > > Twitter: davsclaus, fusenews
>>> >> > > Blog: http://davsclaus.blogspot.com/
>>> >> > > Author of Camel in Action: http://www.manning.com/ibsen/
>>> > --
>>> > Daniel Kulp
>>> > [hidden email] - 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: [hidden email]
>>> 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: [hidden email]
> 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: [hidden email]
Web: http://fusesource.com
Twitter: davsclaus, fusenews
Blog: http://davsclaus.blogspot.com/
Author of Camel in Action: http://www.manning.com/ibsen/

[Claus Ibsen-2]

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 <[hidden email]> 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 <[hidden email]> 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 support.
>>
>> 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üller
>> <[hidden email]> 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 <[hidden email]> wrote:
>>>
>>>> On Tue, May 8, 2012 at 9:02 PM, Daniel Kulp <[hidden email]> 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 use.
>>>> A bit odd as some of these components ought to use the free port finder.
>>>>
>>>>
>>>> > :-)
>>>> >
>>>> > Most of the test failures are with SSL related tests.  They pass on my
>>>> > machine fine so it's a bit concerning to me.  However, I always have the
>>>> > unlimited strength crypto things installed due to my work on the
>>>> ws-security
>>>> > things and wss4j and such.  I'm not sure it that may be part of it or not
>>>> > yet.   I'd have to setup a separate JDK setup to test that.  Can 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üller wrote:
>>>> >> > For private reasons I cannot work on Camel 2.10.0 as I want. I will do
>>>> >> > my
>>>> >> > best to resolve my two outstanding issues in the next week. If this 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 worked on
>>>> >> > (it's not assigned to anybody at present) and which should be resolved
>>>> >> > 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 build
>>>> >> > results are here [1].
>>>> >>
>>>> >> I've pretty much picked this up for you.   I'm at a point now where all
>>>> of
>>>> >> Camel *BUILDS* other that quickfix.   All of the component/* unit tests
>>>> >> now pass as well (although some randomly fail, but that's no different
>>>> >> than with J6).   I'm getting a bunch of failures in the itests.   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 <[hidden email]>
>>>> > wrote:
>>>> >> > > Hi
>>>> >> > >
>>>> >> > > I think its time we start close down on a Camel 2.10 release. The
>>>> >> > > 2.9.0 release was on January 1sy 2012, so its been 4.5 months since
>>>> >> > > that release. Yes in between there has been 2 patch releases, eg
>>>> >> > > 2.9.1, and 2.9.2 etc.
>>>> >> > >
>>>> >> > > There is some new components added in Camel 2.10, and most of them
>>>> 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 easy
>>>> as
>>>> >> > > it would be a copy, and then some adjustments. The camel-leveldb 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 camel-jms
>>>> >> > > testing, to ensure we test against that release.
>>>> >> > >
>>>> >> > > In the JIRA tracker there is 70+ unresolved tickets scheduled for
>>>> 2.10
>>>> >> > >
>>>> >> > >
>>>> https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&j
>>>> >> > > ql
>>>> >> > >
>>>> Query=project+%3D+CAMEL+AND+fixVersion+%3D+%222.10.0%22+AND+resolution
>>>> >> > > +%
>>>> >> > > 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 this
>>>> >> > > version.
>>>> >> > >
>>>> >> > >
>>>> >> > > --
>>>> >> > > Claus Ibsen
>>>> >> > > -----------------
>>>> >> > > CamelOne 2012 Conference, May 15-16, 2012: http://camelone.com
>>>> >> > > FuseSource
>>>> >> > > Email: [hidden email]
>>>> >> > > Web: http://fusesource.com
>>>> >> > > Twitter: davsclaus, fusenews
>>>> >> > > Blog: http://davsclaus.blogspot.com/
>>>> >> > > Author of Camel in Action: http://www.manning.com/ibsen/
>>>> > --
>>>> > Daniel Kulp
>>>> > [hidden email] - 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: [hidden email]
>>>> 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: [hidden email]
>> 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: [hidden email]
> 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: [hidden email]
Web: http://fusesource.com
Twitter: davsclaus, fusenews
Blog: http://davsclaus.blogspot.com/
Author of Camel in Action: http://www.manning.com/ibsen/

[Raul Kripalani-2]

Hi

Found what looks like a bug in camel-blueprint:
https://issues.apache.org/jira/browse/CAMEL-5299. It would seem reasonable
to fix it before 2.10.

It basically renders EventNotifiers unusable in Blueprint. Not very
familiar with Blueprint internals, and this is pretty critical init stuff,
so I might take some time to submit a patch. Is someone willing to take a
stab? (Let me know so we don't duplicate work).

Thanks,

*Raúl Kripalani*
Principal Consultant | FuseSource Corp.
[hidden email] | fusesource.com <http://www.fusesource.com/>
skype: raul.fuse | twitter: @raulvk <http://twitter.com/raulvk>,
@fusenews<http://twitter.com/fusenews>

<http://twitter.com/fusenews>

On 22 May 2012 14:18, Claus Ibsen <[hidden email]> wrote:

> 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 <[hidden email]>
> 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 <[hidden email]>
> 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
> support.
> >>
> >> 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üller
> >> <[hidden email]> 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 <[hidden email]>
> wrote:
> >>>
> >>>> On Tue, May 8, 2012 at 9:02 PM, Daniel Kulp <[hidden email]> 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
> use.
> >>>> A bit odd as some of these components ought to use the free port
> finder.
> >>>>
> >>>>
> >>>> > :-)
> >>>> >
> >>>> > Most of the test failures are with SSL related tests.  They pass on
> my
> >>>> > machine fine so it's a bit concerning to me.  However, I always
> have the
> >>>> > unlimited strength crypto things installed due to my work on the
> >>>> ws-security
> >>>> > things and wss4j and such.  I'm not sure it that may be part of it
> or not
> >>>> > yet.   I'd have to setup a separate JDK setup to test that.  Can
> 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üller wrote:
> >>>> >> > For private reasons I cannot work on Camel 2.10.0 as I want. I
> will do
> >>>> >> > my
> >>>> >> > best to resolve my two outstanding issues in the next week. If
> this 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
> worked on
> >>>> >> > (it's not assigned to anybody at present) and which should be
> resolved
> >>>> >> > 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
> build
> >>>> >> > results are here [1].
> >>>> >>
> >>>> >> I've pretty much picked this up for you.   I'm at a point now
> where all
> >>>> of
> >>>> >> Camel *BUILDS* other that quickfix.   All of the component/* unit
> tests
> >>>> >> now pass as well (although some randomly fail, but that's no
> different
> >>>> >> than with J6).   I'm getting a bunch of failures in the itests.
> 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 <
> [hidden email]>
> >>>> > wrote:
> >>>> >> > > Hi
> >>>> >> > >
> >>>> >> > > I think its time we start close down on a Camel 2.10 release.
> The
> >>>> >> > > 2.9.0 release was on January 1sy 2012, so its been 4.5 months
> since
> >>>> >> > > that release. Yes in between there has been 2 patch releases,
> eg
> >>>> >> > > 2.9.1, and 2.9.2 etc.
> >>>> >> > >
> >>>> >> > > There is some new components added in Camel 2.10, and most of
> them
> >>>> 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
> easy
> >>>> as
> >>>> >> > > it would be a copy, and then some adjustments. The
> camel-leveldb 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
> camel-jms
> >>>> >> > > testing, to ensure we test against that release.
> >>>> >> > >
> >>>> >> > > In the JIRA tracker there is 70+ unresolved tickets scheduled
> for
> >>>> 2.10
> >>>> >> > >
> >>>> >> > >
> >>>>
> https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&j
> >>>> >> > > ql
> >>>> >> > >
> >>>> Query=project+%3D+CAMEL+AND+fixVersion+%3D+%222.10.0%22+AND+resolution
> >>>> >> > > +%
> >>>> >> > > 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
> this
> >>>> >> > > version.
> >>>> >> > >
> >>>> >> > >
> >>>> >> > > --
> >>>> >> > > Claus Ibsen
> >>>> >> > > -----------------
> >>>> >> > > CamelOne 2012 Conference, May 15-16, 2012: http://camelone.com
> >>>> >> > > FuseSource
> >>>> >> > > Email: [hidden email]
> >>>> >> > > Web: http://fusesource.com
> >>>> >> > > Twitter: davsclaus, fusenews
> >>>> >> > > Blog: http://davsclaus.blogspot.com/
> >>>> >> > > Author of Camel in Action: http://www.manning.com/ibsen/
> >>>> > --
> >>>> > Daniel Kulp
> >>>> > [hidden email] - 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: [hidden email]
> >>>> 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: [hidden email]
> >> 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: [hidden email]
> > 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: [hidden email]
> Web: http://fusesource.com
> Twitter: davsclaus, fusenews
> Blog: http://davsclaus.blogspot.com/
> Author of Camel in Action: http://www.manning.com/ibsen/
>

[Claus Ibsen-2]

Hi

The blueprint issue have been fixed, and backported to 2.9 as well.

The Java 7 upgrades seems really good now.
I can test all components, examples etc on my windows xp box.

Only the osgi have a little issue with pax-exam locking the files, and
cannot rename downloaded bundles etc.
Thats a problem with pax-exam and not Camel.

On the ASF CI servers the java7 tests is also good, they only fail due
concurrent testing with the -T option,
which triggers a race condition to find a free port number, and
causing a "Address already in use" failures.

I will look into that later, to improve the camel-test
AvailablePortFinder, to use files to lock a given port number,
so concurrent JVMs can't compete for the same number.


On Tue, May 22, 2012 at 8:19 PM, Raul Kripalani <[hidden email]> wrote:

> Hi
>
> Found what looks like a bug in camel-blueprint:
> https://issues.apache.org/jira/browse/CAMEL-5299. It would seem reasonable
> to fix it before 2.10.
>
> It basically renders EventNotifiers unusable in Blueprint. Not very
> familiar with Blueprint internals, and this is pretty critical init stuff,
> so I might take some time to submit a patch. Is someone willing to take a
> stab? (Let me know so we don't duplicate work).
>
> Thanks,
>
> *Raúl Kripalani*
> Principal Consultant | FuseSource Corp.
> [hidden email] | fusesource.com <http://www.fusesource.com/>
> skype: raul.fuse | twitter: @raulvk <http://twitter.com/raulvk>,
> @fusenews<http://twitter.com/fusenews>
>
> <http://twitter.com/fusenews>
>
> On 22 May 2012 14:18, Claus Ibsen <[hidden email]> wrote:
>
>> 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 <[hidden email]>
>> 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 <[hidden email]>
>> 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
>> support.
>> >>
>> >> 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üller
>> >> <[hidden email]> 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 <[hidden email]>
>> wrote:
>> >>>
>> >>>> On Tue, May 8, 2012 at 9:02 PM, Daniel Kulp <[hidden email]> 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
>> use.
>> >>>> A bit odd as some of these components ought to use the free port
>> finder.
>> >>>>
>> >>>>
>> >>>> > :-)
>> >>>> >
>> >>>> > Most of the test failures are with SSL related tests.  They pass on
>> my
>> >>>> > machine fine so it's a bit concerning to me.  However, I always
>> have the
>> >>>> > unlimited strength crypto things installed due to my work on the
>> >>>> ws-security
>> >>>> > things and wss4j and such.  I'm not sure it that may be part of it
>> or not
>> >>>> > yet.   I'd have to setup a separate JDK setup to test that.  Can
>> 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üller wrote:
>> >>>> >> > For private reasons I cannot work on Camel 2.10.0 as I want. I
>> will do
>> >>>> >> > my
>> >>>> >> > best to resolve my two outstanding issues in the next week. If
>> this 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
>> worked on
>> >>>> >> > (it's not assigned to anybody at present) and which should be
>> resolved
>> >>>> >> > 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
>> build
>> >>>> >> > results are here [1].
>> >>>> >>
>> >>>> >> I've pretty much picked this up for you.   I'm at a point now
>> where all
>> >>>> of
>> >>>> >> Camel *BUILDS* other that quickfix.   All of the component/* unit
>> tests
>> >>>> >> now pass as well (although some randomly fail, but that's no
>> different
>> >>>> >> than with J6).   I'm getting a bunch of failures in the itests.
>> 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 <
>> [hidden email]>
>> >>>> > wrote:
>> >>>> >> > > Hi
>> >>>> >> > >
>> >>>> >> > > I think its time we start close down on a Camel 2.10 release.
>> The
>> >>>> >> > > 2.9.0 release was on January 1sy 2012, so its been 4.5 months
>> since
>> >>>> >> > > that release. Yes in between there has been 2 patch releases,
>> eg
>> >>>> >> > > 2.9.1, and 2.9.2 etc.
>> >>>> >> > >
>> >>>> >> > > There is some new components added in Camel 2.10, and most of
>> them
>> >>>> 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
>> easy
>> >>>> as
>> >>>> >> > > it would be a copy, and then some adjustments. The
>> camel-leveldb 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
>> camel-jms
>> >>>> >> > > testing, to ensure we test against that release.
>> >>>> >> > >
>> >>>> >> > > In the JIRA tracker there is 70+ unresolved tickets scheduled
>> for
>> >>>> 2.10
>> >>>> >> > >
>> >>>> >> > >
>> >>>>
>> https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&j
>> >>>> >> > > ql
>> >>>> >> > >
>> >>>> Query=project+%3D+CAMEL+AND+fixVersion+%3D+%222.10.0%22+AND+resolution
>> >>>> >> > > +%
>> >>>> >> > > 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
>> this
>> >>>> >> > > version.
>> >>>> >> > >
>> >>>> >> > >
>> >>>> >> > > --
>> >>>> >> > > Claus Ibsen
>> >>>> >> > > -----------------
>> >>>> >> > > CamelOne 2012 Conference, May 15-16, 2012: http://camelone.com
>> >>>> >> > > FuseSource
>> >>>> >> > > Email: [hidden email]
>> >>>> >> > > Web: http://fusesource.com
>> >>>> >> > > Twitter: davsclaus, fusenews
>> >>>> >> > > Blog: http://davsclaus.blogspot.com/
>> >>>> >> > > Author of Camel in Action: http://www.manning.com/ibsen/
>> >>>> > --
>> >>>> > Daniel Kulp
>> >>>> > [hidden email] - 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: [hidden email]
>> >>>> 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: [hidden email]
>> >> 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: [hidden email]
>> > 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: [hidden email]
>> 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: [hidden email]
Web: http://fusesource.com
Twitter: davsclaus, fusenews
Blog: http://davsclaus.blogspot.com/
Author of Camel in Action: http://www.manning.com/ibsen/

[Charles Moulliard]

Hi Claus,

I have finished the modifications (refactor in fact) for camel-websocket
to support ws:// and wss:// protocols. So the timing sounds good to me
to promote soon release 2.10

Nevertheless, I would like to dissuccs the following poitn concerning
Jetty version. We currently use Jetty 7.5.4. According to some
discussions that I have had with Jean François Arcand and its blog,
websocket support in Jetty 7.6.3 and  8.1.3 are stable now which is not
the case with previous versions
(http://jfarcand.wordpress.com/category/websocket-2/). So the point is,
are we ok to migrate to 7.6.3 for apache camel project globally or only
for websocket component ?

Regards,

Charles

On 24/05/12 11:08, Claus Ibsen wrote:

> Hi
>
> The blueprint issue have been fixed, and backported to 2.9 as well.
>
> The Java 7 upgrades seems really good now.
> I can test all components, examples etc on my windows xp box.
>
> Only the osgi have a little issue with pax-exam locking the files, and
> cannot rename downloaded bundles etc.
> Thats a problem with pax-exam and not Camel.
>
> On the ASF CI servers the java7 tests is also good, they only fail due
> concurrent testing with the -T option,
> which triggers a race condition to find a free port number, and
> causing a "Address already in use" failures.
>
> I will look into that later, to improve the camel-test
> AvailablePortFinder, to use files to lock a given port number,
> so concurrent JVMs can't compete for the same number.
>
>
> On Tue, May 22, 2012 at 8:19 PM, Raul Kripalani<[hidden email]>  wrote:
>> Hi
>>
>> Found what looks like a bug in camel-blueprint:
>> https://issues.apache.org/jira/browse/CAMEL-5299. It would seem reasonable
>> to fix it before 2.10.
>>
>> It basically renders EventNotifiers unusable in Blueprint. Not very
>> familiar with Blueprint internals, and this is pretty critical init stuff,
>> so I might take some time to submit a patch. Is someone willing to take a
>> stab? (Let me know so we don't duplicate work).
>>
>> Thanks,
>>
>> *Raúl Kripalani*
>> Principal Consultant | FuseSource Corp.
>> [hidden email] | fusesource.com<http://www.fusesource.com/>
>> skype: raul.fuse | twitter: @raulvk<http://twitter.com/raulvk>,
>> @fusenews<http://twitter.com/fusenews>
>>
>> <http://twitter.com/fusenews>
>>
>> On 22 May 2012 14:18, Claus Ibsen<[hidden email]>  wrote:
>>
>>> 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<[hidden email]>
>>> 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<[hidden email]>
>>> 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
>>> support.
>>>>> 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üller
>>>>> <[hidden email]>  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<[hidden email]>
>>> wrote:
>>>>>>> On Tue, May 8, 2012 at 9:02 PM, Daniel Kulp<[hidden email]>  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
>>> use.
>>>>>>> A bit odd as some of these components ought to use the free port
>>> finder.
>>>>>>>
>>>>>>>> :-)
>>>>>>>>
>>>>>>>> Most of the test failures are with SSL related tests.  They pass on
>>> my
>>>>>>>> machine fine so it's a bit concerning to me.  However, I always
>>> have the
>>>>>>>> unlimited strength crypto things installed due to my work on the
>>>>>>> ws-security
>>>>>>>> things and wss4j and such.  I'm not sure it that may be part of it
>>> or not
>>>>>>>> yet.   I'd have to setup a separate JDK setup to test that.  Can
>>> 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üller wrote:
>>>>>>>>>> For private reasons I cannot work on Camel 2.10.0 as I want. I
>>> will do
>>>>>>>>>> my
>>>>>>>>>> best to resolve my two outstanding issues in the next week. If
>>> this 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
>>> worked on
>>>>>>>>>> (it's not assigned to anybody at present) and which should be
>>> resolved
>>>>>>>>>> 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
>>> build
>>>>>>>>>> results are here [1].
>>>>>>>>> I've pretty much picked this up for you.   I'm at a point now
>>> where all
>>>>>>> of
>>>>>>>>> Camel *BUILDS* other that quickfix.   All of the component/* unit
>>> tests
>>>>>>>>> now pass as well (although some randomly fail, but that's no
>>> different
>>>>>>>>> than with J6).   I'm getting a bunch of failures in the itests.
>>> 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<
>>> [hidden email]>
>>>>>>>> wrote:
>>>>>>>>>>> Hi
>>>>>>>>>>>
>>>>>>>>>>> I think its time we start close down on a Camel 2.10 release.
>>> The
>>>>>>>>>>> 2.9.0 release was on January 1sy 2012, so its been 4.5 months
>>> since
>>>>>>>>>>> that release. Yes in between there has been 2 patch releases,
>>> eg
>>>>>>>>>>> 2.9.1, and 2.9.2 etc.
>>>>>>>>>>>
>>>>>>>>>>> There is some new components added in Camel 2.10, and most of
>>> them
>>>>>>> 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
>>> easy
>>>>>>> as
>>>>>>>>>>> it would be a copy, and then some adjustments. The
>>> camel-leveldb 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
>>> camel-jms
>>>>>>>>>>> testing, to ensure we test against that release.
>>>>>>>>>>>
>>>>>>>>>>> In the JIRA tracker there is 70+ unresolved tickets scheduled
>>> for
>>>>>>> 2.10
>>>>>>>>>>>
>>> https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&j
>>>>>>>>>>> ql
>>>>>>>>>>>
>>>>>>> Query=project+%3D+CAMEL+AND+fixVersion+%3D+%222.10.0%22+AND+resolution
>>>>>>>>>>> +%
>>>>>>>>>>> 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
>>> this
>>>>>>>>>>> version.
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> --
>>>>>>>>>>> Claus Ibsen
>>>>>>>>>>> -----------------
>>>>>>>>>>> CamelOne 2012 Conference, May 15-16, 2012: http://camelone.com
>>>>>>>>>>> FuseSource
>>>>>>>>>>> Email: [hidden email]
>>>>>>>>>>> Web: http://fusesource.com
>>>>>>>>>>> Twitter: davsclaus, fusenews
>>>>>>>>>>> Blog: http://davsclaus.blogspot.com/
>>>>>>>>>>> Author of Camel in Action: http://www.manning.com/ibsen/
>>>>>>>> --
>>>>>>>> Daniel Kulp
>>>>>>>> [hidden email] - 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: [hidden email]
>>>>>>> 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: [hidden email]
>>>>> 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: [hidden email]
>>>> 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: [hidden email]
>>> Web: http://fusesource.com
>>> Twitter: davsclaus, fusenews
>>> Blog: http://davsclaus.blogspot.com/
>>> Author of Camel in Action: http://www.manning.com/ibsen/
>>>
>
>

[Christian Mueller]

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?

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.

Best,
Christian

On Thu, May 24, 2012 at 12:25 PM, Charles Moulliard <[hidden email]>wrote:

> Hi Claus,
>
> I have finished the modifications (refactor in fact) for camel-websocket
> to support ws:// and wss:// protocols. So the timing sounds good to me to
> promote soon release 2.10
>
> Nevertheless, I would like to dissuccs the following poitn concerning
> Jetty version. We currently use Jetty 7.5.4. According to some discussions
> that I have had with Jean François Arcand and its blog, websocket support
> in Jetty 7.6.3 and  8.1.3 are stable now which is not the case with
> previous versions (http://jfarcand.wordpress.**com/category/websocket-2/<http://jfarcand.wordpress.com/category/websocket-2/>).
> So the point is, are we ok to migrate to 7.6.3 for apache camel project
> globally or only for websocket component ?
>
> Regards,
>
> Charles
>
>
> On 24/05/12 11:08, Claus Ibsen wrote:
>
>> Hi
>>
>> The blueprint issue have been fixed, and backported to 2.9 as well.
>>
>> The Java 7 upgrades seems really good now.
>> I can test all components, examples etc on my windows xp box.
>>
>> Only the osgi have a little issue with pax-exam locking the files, and
>> cannot rename downloaded bundles etc.
>> Thats a problem with pax-exam and not Camel.
>>
>> On the ASF CI servers the java7 tests is also good, they only fail due
>> concurrent testing with the -T option,
>> which triggers a race condition to find a free port number, and
>> causing a "Address already in use" failures.
>>
>> I will look into that later, to improve the camel-test
>> AvailablePortFinder, to use files to lock a given port number,
>> so concurrent JVMs can't compete for the same number.
>>
>>
>> On Tue, May 22, 2012 at 8:19 PM, Raul Kripalani<[hidden email]>
>>  wrote:
>>
>>> Hi
>>>
>>> Found what looks like a bug in camel-blueprint:
>>> https://issues.apache.org/**jira/browse/CAMEL-5299<https://issues.apache.org/jira/browse/CAMEL-5299>.
>>> It would seem reasonable
>>> to fix it before 2.10.
>>>
>>> It basically renders EventNotifiers unusable in Blueprint. Not very
>>> familiar with Blueprint internals, and this is pretty critical init
>>> stuff,
>>> so I might take some time to submit a patch. Is someone willing to take a
>>> stab? (Let me know so we don't duplicate work).
>>>
>>> Thanks,
>>>
>>> *Raúl Kripalani*
>>> Principal Consultant | FuseSource Corp.
>>> [hidden email] | fusesource.com<http://www.**fusesource.com/<http://www.fusesource.com/>
>>> >
>>> skype: raul.fuse | twitter: @raulvk<http://twitter.com/**raulvk<http://twitter.com/raulvk>
>>> >,
>>> @fusenews<http://twitter.com/**fusenews <http://twitter.com/fusenews>>
>>>
>>> <http://twitter.com/fusenews>
>>>
>>> On 22 May 2012 14:18, Claus Ibsen<[hidden email]>  wrote:
>>>
>>>  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<[hidden email]>
>>>> 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<[hidden email]>
>>>>>
>>>> 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
>>>>>>
>>>>> support.
>>>>
>>>>> 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üller
>>>>>> <[hidden email]>  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<[hidden email]>
>>>>>>>
>>>>>> wrote:
>>>>
>>>>> On Tue, May 8, 2012 at 9:02 PM, Daniel Kulp<[hidden email]>  wrote:
>>>>>>>>
>>>>>>>>> The latest Jenkins build definitely looks a TON better:
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> https://builds.apache.org/job/**Camel.trunk.fulltest.java7/82/<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
>>>>>>>>
>>>>>>> use.
>>>>
>>>>> A bit odd as some of these components ought to use the free port
>>>>>>>>
>>>>>>> finder.
>>>>
>>>>>
>>>>>>>>  :-)
>>>>>>>>>
>>>>>>>>> Most of the test failures are with SSL related tests.  They pass on
>>>>>>>>>
>>>>>>>> my
>>>>
>>>>> machine fine so it's a bit concerning to me.  However, I always
>>>>>>>>>
>>>>>>>> have the
>>>>
>>>>> unlimited strength crypto things installed due to my work on the
>>>>>>>>>
>>>>>>>> ws-security
>>>>>>>>
>>>>>>>>> things and wss4j and such.  I'm not sure it that may be part of it
>>>>>>>>>
>>>>>>>> or not
>>>>
>>>>> yet.   I'd have to setup a separate JDK setup to test that.  Can
>>>>>>>>>
>>>>>>>> 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üller wrote:
>>>>>>>>>>
>>>>>>>>>>> For private reasons I cannot work on Camel 2.10.0 as I want. I
>>>>>>>>>>>
>>>>>>>>>> will do
>>>>
>>>>> my
>>>>>>>>>>> best to resolve my two outstanding issues in the next week. If
>>>>>>>>>>>
>>>>>>>>>> this 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
>>>>>>>>>>>
>>>>>>>>>> worked on
>>>>
>>>>> (it's not assigned to anybody at present) and which should be
>>>>>>>>>>>
>>>>>>>>>> resolved
>>>>
>>>>> 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
>>>>>>>>>>>
>>>>>>>>>> build
>>>>
>>>>> results are here [1].
>>>>>>>>>>>
>>>>>>>>>> I've pretty much picked this up for you.   I'm at a point now
>>>>>>>>>>
>>>>>>>>> where all
>>>>
>>>>> of
>>>>>>>>
>>>>>>>>> Camel *BUILDS* other that quickfix.   All of the component/* unit
>>>>>>>>>>
>>>>>>>>> tests
>>>>
>>>>> now pass as well (although some randomly fail, but that's no
>>>>>>>>>>
>>>>>>>>> different
>>>>
>>>>> than with J6).   I'm getting a bunch of failures in the itests.
>>>>>>>>>>
>>>>>>>>> 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<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<
>>>>>>>>>>>
>>>>>>>>>> [hidden email]>
>>>>
>>>>> wrote:
>>>>>>>>>
>>>>>>>>>> Hi
>>>>>>>>>>>>
>>>>>>>>>>>> I think its time we start close down on a Camel 2.10 release.
>>>>>>>>>>>>
>>>>>>>>>>> The
>>>>
>>>>> 2.9.0 release was on January 1sy 2012, so its been 4.5 months
>>>>>>>>>>>>
>>>>>>>>>>> since
>>>>
>>>>> that release. Yes in between there has been 2 patch releases,
>>>>>>>>>>>>
>>>>>>>>>>> eg
>>>>
>>>>> 2.9.1, and 2.9.2 etc.
>>>>>>>>>>>>
>>>>>>>>>>>> There is some new components added in Camel 2.10, and most of
>>>>>>>>>>>>
>>>>>>>>>>> them
>>>>
>>>>> 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
>>>>>>>>>>>>
>>>>>>>>>>> easy
>>>>
>>>>> as
>>>>>>>>
>>>>>>>>> it would be a copy, and then some adjustments. The
>>>>>>>>>>>>
>>>>>>>>>>> camel-leveldb 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
>>>>>>>>>>>>
>>>>>>>>>>> camel-jms
>>>>
>>>>> testing, to ensure we test against that release.
>>>>>>>>>>>>
>>>>>>>>>>>> In the JIRA tracker there is 70+ unresolved tickets scheduled
>>>>>>>>>>>>
>>>>>>>>>>> for
>>>>
>>>>> 2.10
>>>>>>>>
>>>>>>>>>
>>>>>>>>>>>>  https://issues.apache.org/**jira/secure/IssueNavigator.**
>>>> jspa?reset=true&j<https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&j>
>>>>
>>>>> ql
>>>>>>>>>>>>
>>>>>>>>>>>>  Query=project+%3D+CAMEL+AND+**fixVersion+%3D+%222.10.0%22+**
>>>>>>>> AND+resolution
>>>>>>>>
>>>>>>>>> +%
>>>>>>>>>>>> 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
>>>>>>>>>>>>
>>>>>>>>>>> this
>>>>
>>>>> version.
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> --
>>>>>>>>>>>> Claus Ibsen
>>>>>>>>>>>> -----------------
>>>>>>>>>>>> CamelOne 2012 Conference, May 15-16, 2012: http://camelone.com
>>>>>>>>>>>> FuseSource
>>>>>>>>>>>> Email: [hidden email]
>>>>>>>>>>>> Web: http://fusesource.com
>>>>>>>>>>>> Twitter: davsclaus, fusenews
>>>>>>>>>>>> Blog: http://davsclaus.blogspot.com/
>>>>>>>>>>>> Author of Camel in Action: http://www.manning.com/ibsen/
>>>>>>>>>>>>
>>>>>>>>>>> --
>>>>>>>>> Daniel Kulp
>>>>>>>>> [hidden email] - 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: [hidden email]
>>>>>>>> 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: [hidden email]
>>>>>> 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: [hidden email]
>>>>> 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: [hidden email]
>>>> Web: http://fusesource.com
>>>> Twitter: davsclaus, fusenews
>>>> Blog: http://davsclaus.blogspot.com/
>>>> Author of Camel in Action: http://www.manning.com/ibsen/
>>>>
>>>>
>>
>>

[Daniel Kulp]

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
[hidden email]
http://dankulp.com/blog

[Claus Ibsen-2]

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 <[hidden email]> 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
> [hidden email]
> http://dankulp.com/blog
>

--
Claus Ibsen
-----------------
FuseSource
Email: [hidden email]
Web: http://fusesource.com
Twitter: davsclaus, fusenews
Blog: http://davsclaus.com
Author of Camel in Action: http://www.manning.com/ibsen

On Saturday, June 02, 2012 02:57:56 PM Claus Ibsen 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.

Could we NOT do that and just un-assign a fix-version in the future?   If
someone is not actively working on it, it shouldn't have a version (or a an
assignee).    People may see those and say "oh, someone is fixing it for
2.11, cool" and then 2.11 comes along and it gets moved.

Dan

>
> 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 <[hidden email]> 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
> > [hidden email]
> > http://dankulp.com/blog

--
Daniel Kulp
[hidden email] - http://dankulp.com/blog
Talend Community Coder - http://coders.talend.com

[David J. M. Karlsen]

+1 to that.

2012/6/2 Daniel Kulp <[hidden email]>:

> On Saturday, June 02, 2012 02:57:56 PM Claus Ibsen 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.
>
> Could we NOT do that and just un-assign a fix-version in the future?   If
> someone is not actively working on it, it shouldn't have a version (or a an
> assignee).    People may see those and say "oh, someone is fixing it for
> 2.11, cool" and then 2.11 comes along and it gets moved.
>
> Dan
>
>>
>> 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 <[hidden email]> 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
>> > [hidden email]
>> > http://dankulp.com/blog
> --
> Daniel Kulp
> [hidden email] - http://dankulp.com/blog
> Talend Community Coder - http://coders.talend.com
>

--
--
David J. M. Karlsen - http://www.linkedin.com/in/davidkarlsen