You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by Claus Ibsen <cl...@gmail.com> on 2013/04/02 16:57:07 UTC
Re: [DISCUSS] - Moving towards Camel 2.11 release
On Fri, Mar 29, 2013 at 7:10 PM, Hadrian Zbarcea <hz...@gmail.com> wrote:
> I have been advised to wait for the cxf-2.7.4 release, currently under vote.
> It has some rather important issues that we probably want to take. CXF
> committers on this list, please correct me if I am wrong.
>
> As there are already a number of positive votes, I expect the cxf release to
> become public on Mon, so I could build 2.11.0 on Tue.
>
Sounds good.
I think the code base is ready for a RC.
> Cheers,
> Hadrian
>
>
>
> On 03/28/2013 08:18 AM, Hadrian Zbarcea wrote:
>>
>> Christian, do you want to build this release or you want me to do it?
>> I'd also suggest doing a full build/test before the dryRun.
>>
>> Hadrian
>>
>>
>>
>> On 03/28/2013 05:22 AM, Christian Müller wrote:
>>>
>>> Ok, I fixed [1] and removed it from the official Apache Camel SVN and
>>> update the docs. I will commit it into Camel Extra and add the docs there
>>> in a few minutes/hours.
>>>
>>> We only have two outstanding issues [2].
>>>
>>> I will run a "mvn release:prepare -DdryRun=true" to check whether I hit
>>> some issues.
>>> Do we already have a release manager for Camel 2.11 (to make sure
>>> nobody is
>>> waiting for somebody)?
>>>
>>> [1] https://issues.apache.org/jira/browse/CAMEL-5483
>>> [2]
>>>
>>> https://issues.apache.org/jira/issues/?jql=project%20%3D%20CAMEL%20AND%20resolution%20%3D%20Unresolved%20AND%20fixVersion%20%3D%20%222.11.0%22
>>>
>>>
>>> Best,
>>> Christian
>>>
>>> On Thu, Mar 28, 2013 at 2:18 AM, Raul Kripalani <ra...@evosent.com> wrote:
>>>
>>>> Hi,
>>>>
>>>> Managed to find time to commit the improvement for CAMEL-5698.
>>>>
>>>> For CAMEL-5916 the fix is almost ready. Hopefully I'll reach in time
>>>> before
>>>> we cut the release. It'll be a great improvement for the usability of
>>>> camel-cxfrs.
>>>>
>>>> Regards,
>>>> Raúl.
>>>>
>>>> On Wed, Mar 27, 2013 at 1:30 PM, Claus Ibsen <cl...@gmail.com>
>>>> wrote:
>>>>
>>>>> Hi
>>>>>
>>>>> Oh yeah and CAMEL-5483 is a issue we must resolve. I think Hadrian is
>>>>> working on that.
>>>>>
>>>>>
>>>>> On Wed, Mar 27, 2013 at 2:25 PM, Claus Ibsen <cl...@gmail.com>
>>>>> wrote:
>>>>>>
>>>>>> Hi
>>>>>>
>>>>>> Okay we are getting there. The JIRA tracker has 3 tickets for 2.11.0.
>>>>>>
>>>>>
>>>>
>>>> https://issues.apache.org/jira/issues/?filter=12315472&jql=project%20%3D%20CAMEL%20AND%20resolution%20%3D%20Unresolved%20AND%20fixVersion%20%3D%20%222.11.0%22
>>>>
>>>>>>
>>>>>> And I think Willem have almost/done his 2 tickets.
>>>>>>
>>>>>> And the last ticket CAMEL-6042 requires some documentation about this
>>>>>> new functionality. I have asked Aaron to help with that. And it would
>>>>>> be great with a better set of unit tests as well.
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Claus Ibsen
>>>>>> -----------------
>>>>>> Red Hat, Inc.
>>>>>> FuseSource is now part of Red Hat
>>>>>> Email: cibsen@redhat.com
>>>>>> Web: http://fusesource.com
>>>>>> Twitter: davsclaus
>>>>>> Blog: http://davsclaus.com
>>>>>> Author of Camel in Action: http://www.manning.com/ibsen
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Claus Ibsen
>>>>> -----------------
>>>>> Red Hat, Inc.
>>>>> FuseSource is now part of Red Hat
>>>>> Email: cibsen@redhat.com
>>>>> Web: http://fusesource.com
>>>>> Twitter: davsclaus
>>>>> Blog: http://davsclaus.com
>>>>> Author of Camel in Action: http://www.manning.com/ibsen
>>>>>
>>>>
>>>
>
--
Claus Ibsen
-----------------
Red Hat, Inc.
FuseSource is now part of Red Hat
Email: cibsen@redhat.com
Web: http://fusesource.com
Twitter: davsclaus
Blog: http://davsclaus.com
Author of Camel in Action: http://www.manning.com/ibsen
Re: [DISCUSS] - Moving towards Camel 2.11 release
Posted by Christian Müller <ch...@gmail.com>.
camel-example-cxf-blueprint 2.11-SNAPSHOT is now working on my Karaf 2.3.1
installation after adding the feature camel-blueprint.
Best,
Christian
On Fri, Apr 5, 2013 at 9:10 PM, Babak Vahdat <ba...@swissonline.ch>wrote:
> Hi
>
> I've already fixed the failed camel-aws test on Windows as now the
> InputStream gets closed properly in case the DeleteAfterWrite option is
> enabled by the S3Producer.
>
> Babak
>
>
> Claus Ibsen-2 wrote
> > Hi
> >
> > Okay so we have 2 issues
> >
> > - a test in camel-aws fails on Windows.
> > - camel:run in blueprint does not work
> >
> > I will work on the latter tomorrow morning.
> > And then look at the failing test on Windows (it indicate a problem
> > with not closing a file input stream, causing the file to be locked).
> >
> > IMHO we should have these 2 fixed before we can cut the RC.
> >
> >
> >
> >
> > On Fri, Apr 5, 2013 at 4:09 PM, Claus Ibsen <
>
> > claus.ibsen@
>
> > > wrote:
> >> Hi
> >>
> >> I am running a full test on Windows.
> >>
> >> There is a single test in camel-aws that fails. I guess its related to
> >> not being able to delete the file.
> >> Will dig into this later when getting a bit of time. Either later
> >> today or tomorrow morning.
> >>
> >> If anyone on Windows, then feel free to look into that failing test so
> >> we can have it fixed before cutting the 2.11 release.
> >>
> >>
> >> On Fri, Apr 5, 2013 at 12:32 PM, Claus Ibsen <
>
> > claus.ibsen@
>
> > > wrote:
> >>> Just a note to us that we should remember checkin the maven archetype
> >>> for the blueprint.
> >>> There may be a problem with 2x blueprint on the classpath when using
> >>> camel:run
> >>>
> >>> On Fri, Apr 5, 2013 at 12:13 PM, Jan Matèrne (jhm) <
>
> > apache@
>
> > > wrote:
> >>>>> There is a new Apache SMX bundle in VOTE just now.
> >>>>> Wonder if we should wait for this release so the Camel bundles can
> use
> >>>>> these upgrades?
> >>>>> Or maybe we want to get the 2.11 out sooner?
> >>>>
> >>>> I think there always will be a coming release and you should not try
> to
> >>>> catch all of them.
> >>>> You could upgrade with a 2.12 if necessary.
> >>>>
> >>>> Just my 2ct
> >>>> Jan
> >>>>
> >>>
> >>>
> >>>
> >>> --
> >>> Claus Ibsen
> >>> -----------------
> >>> Red Hat, Inc.
> >>> FuseSource is now part of Red Hat
> >>> Email:
>
> > cibsen@
>
> >>> Web: http://fusesource.com
> >>> Twitter: davsclaus
> >>> Blog: http://davsclaus.com
> >>> Author of Camel in Action: http://www.manning.com/ibsen
> >>
> >>
> >>
> >> --
> >> Claus Ibsen
> >> -----------------
> >> Red Hat, Inc.
> >> FuseSource is now part of Red Hat
> >> Email:
>
> > cibsen@
>
> >> Web: http://fusesource.com
> >> Twitter: davsclaus
> >> Blog: http://davsclaus.com
> >> Author of Camel in Action: http://www.manning.com/ibsen
> >
> >
> >
> > --
> > Claus Ibsen
> > -----------------
> > Red Hat, Inc.
> > FuseSource is now part of Red Hat
> > Email:
>
> > cibsen@
>
> > Web: http://fusesource.com
> > Twitter: davsclaus
> > Blog: http://davsclaus.com
> > Author of Camel in Action: http://www.manning.com/ibsen
>
>
>
>
>
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/DISCUSS-Moving-towards-Camel-2-11-release-tp5725088p5730424.html
> Sent from the Camel Development mailing list archive at Nabble.com.
>
Re: [DISCUSS] - Moving towards Camel 2.11 release
Posted by Babak Vahdat <ba...@swissonline.ch>.
Hi
I've already fixed the failed camel-aws test on Windows as now the
InputStream gets closed properly in case the DeleteAfterWrite option is
enabled by the S3Producer.
Babak
Claus Ibsen-2 wrote
> Hi
>
> Okay so we have 2 issues
>
> - a test in camel-aws fails on Windows.
> - camel:run in blueprint does not work
>
> I will work on the latter tomorrow morning.
> And then look at the failing test on Windows (it indicate a problem
> with not closing a file input stream, causing the file to be locked).
>
> IMHO we should have these 2 fixed before we can cut the RC.
>
>
>
>
> On Fri, Apr 5, 2013 at 4:09 PM, Claus Ibsen <
> claus.ibsen@
> > wrote:
>> Hi
>>
>> I am running a full test on Windows.
>>
>> There is a single test in camel-aws that fails. I guess its related to
>> not being able to delete the file.
>> Will dig into this later when getting a bit of time. Either later
>> today or tomorrow morning.
>>
>> If anyone on Windows, then feel free to look into that failing test so
>> we can have it fixed before cutting the 2.11 release.
>>
>>
>> On Fri, Apr 5, 2013 at 12:32 PM, Claus Ibsen <
> claus.ibsen@
> > wrote:
>>> Just a note to us that we should remember checkin the maven archetype
>>> for the blueprint.
>>> There may be a problem with 2x blueprint on the classpath when using
>>> camel:run
>>>
>>> On Fri, Apr 5, 2013 at 12:13 PM, Jan Matèrne (jhm) <
> apache@
> > wrote:
>>>>> There is a new Apache SMX bundle in VOTE just now.
>>>>> Wonder if we should wait for this release so the Camel bundles can use
>>>>> these upgrades?
>>>>> Or maybe we want to get the 2.11 out sooner?
>>>>
>>>> I think there always will be a coming release and you should not try to
>>>> catch all of them.
>>>> You could upgrade with a 2.12 if necessary.
>>>>
>>>> Just my 2ct
>>>> Jan
>>>>
>>>
>>>
>>>
>>> --
>>> Claus Ibsen
>>> -----------------
>>> Red Hat, Inc.
>>> FuseSource is now part of Red Hat
>>> Email:
> cibsen@
>>> Web: http://fusesource.com
>>> Twitter: davsclaus
>>> Blog: http://davsclaus.com
>>> Author of Camel in Action: http://www.manning.com/ibsen
>>
>>
>>
>> --
>> Claus Ibsen
>> -----------------
>> Red Hat, Inc.
>> FuseSource is now part of Red Hat
>> Email:
> cibsen@
>> Web: http://fusesource.com
>> Twitter: davsclaus
>> Blog: http://davsclaus.com
>> Author of Camel in Action: http://www.manning.com/ibsen
>
>
>
> --
> Claus Ibsen
> -----------------
> Red Hat, Inc.
> FuseSource is now part of Red Hat
> Email:
> cibsen@
> Web: http://fusesource.com
> Twitter: davsclaus
> Blog: http://davsclaus.com
> Author of Camel in Action: http://www.manning.com/ibsen
--
View this message in context: http://camel.465427.n5.nabble.com/DISCUSS-Moving-towards-Camel-2-11-release-tp5725088p5730424.html
Sent from the Camel Development mailing list archive at Nabble.com.
Re: [DISCUSS] - Moving towards Camel 2.11 release
Posted by Claus Ibsen <cl...@gmail.com>.
Hi
I have fixed the blueprint problem with camel:run
https://issues.apache.org/jira/browse/CAMEL-6244
Which actually also could be a problem for testing with
camel-test-blueprint. So this should be better now.
And the Windows test is also fixed. So we are looking into good shape.
On Fri, Apr 5, 2013 at 6:16 PM, Claus Ibsen <cl...@gmail.com> wrote:
> Hi
>
> Okay so we have 2 issues
>
> - a test in camel-aws fails on Windows.
> - camel:run in blueprint does not work
>
> I will work on the latter tomorrow morning.
> And then look at the failing test on Windows (it indicate a problem
> with not closing a file input stream, causing the file to be locked).
>
> IMHO we should have these 2 fixed before we can cut the RC.
>
>
>
>
> On Fri, Apr 5, 2013 at 4:09 PM, Claus Ibsen <cl...@gmail.com> wrote:
>> Hi
>>
>> I am running a full test on Windows.
>>
>> There is a single test in camel-aws that fails. I guess its related to
>> not being able to delete the file.
>> Will dig into this later when getting a bit of time. Either later
>> today or tomorrow morning.
>>
>> If anyone on Windows, then feel free to look into that failing test so
>> we can have it fixed before cutting the 2.11 release.
>>
>>
>> On Fri, Apr 5, 2013 at 12:32 PM, Claus Ibsen <cl...@gmail.com> wrote:
>>> Just a note to us that we should remember checkin the maven archetype
>>> for the blueprint.
>>> There may be a problem with 2x blueprint on the classpath when using camel:run
>>>
>>> On Fri, Apr 5, 2013 at 12:13 PM, Jan Matèrne (jhm) <ap...@materne.de> wrote:
>>>>> There is a new Apache SMX bundle in VOTE just now.
>>>>> Wonder if we should wait for this release so the Camel bundles can use
>>>>> these upgrades?
>>>>> Or maybe we want to get the 2.11 out sooner?
>>>>
>>>> I think there always will be a coming release and you should not try to
>>>> catch all of them.
>>>> You could upgrade with a 2.12 if necessary.
>>>>
>>>> Just my 2ct
>>>> Jan
>>>>
>>>
>>>
>>>
>>> --
>>> Claus Ibsen
>>> -----------------
>>> Red Hat, Inc.
>>> FuseSource is now part of Red Hat
>>> Email: cibsen@redhat.com
>>> Web: http://fusesource.com
>>> Twitter: davsclaus
>>> Blog: http://davsclaus.com
>>> Author of Camel in Action: http://www.manning.com/ibsen
>>
>>
>>
>> --
>> Claus Ibsen
>> -----------------
>> Red Hat, Inc.
>> FuseSource is now part of Red Hat
>> Email: cibsen@redhat.com
>> Web: http://fusesource.com
>> Twitter: davsclaus
>> Blog: http://davsclaus.com
>> Author of Camel in Action: http://www.manning.com/ibsen
>
>
>
> --
> Claus Ibsen
> -----------------
> Red Hat, Inc.
> FuseSource is now part of Red Hat
> Email: cibsen@redhat.com
> Web: http://fusesource.com
> Twitter: davsclaus
> Blog: http://davsclaus.com
> Author of Camel in Action: http://www.manning.com/ibsen
--
Claus Ibsen
-----------------
Red Hat, Inc.
FuseSource is now part of Red Hat
Email: cibsen@redhat.com
Web: http://fusesource.com
Twitter: davsclaus
Blog: http://davsclaus.com
Author of Camel in Action: http://www.manning.com/ibsen
Re: [DISCUSS] - Moving towards Camel 2.11 release
Posted by Christian Müller <ch...@gmail.com>.
Thanks Claus!
I will have a look at this later today and let you know whether I could
find and fix the issue.
But there are still three outstanding issues [1] which prevents me starting
the build.
I think Hadrian already fixed
CAMEL-6234<https://issues.apache.org/jira/browse/CAMEL-6234>.
Right?
Not sure whether Willem is done with
CAMEL-6182<https://issues.apache.org/jira/browse/CAMEL-6182>.
Willem?
CAMEL-6042 <https://issues.apache.org/jira/browse/CAMEL-6042> is only open
for improving the unit test's, Claus?
[1]
https://issues.apache.org/jira/issues/?jql=project%20%3D%20CAMEL%20AND%20resolution%20%3D%20Unresolved%20AND%20fixVersion%20%3D%20%222.11.0%22
Best,
Christian
On Fri, Apr 5, 2013 at 6:16 PM, Claus Ibsen <cl...@gmail.com> wrote:
> Hi
>
> Okay so we have 2 issues
>
> - a test in camel-aws fails on Windows.
> - camel:run in blueprint does not work
>
> I will work on the latter tomorrow morning.
> And then look at the failing test on Windows (it indicate a problem
> with not closing a file input stream, causing the file to be locked).
>
> IMHO we should have these 2 fixed before we can cut the RC.
>
>
>
>
> On Fri, Apr 5, 2013 at 4:09 PM, Claus Ibsen <cl...@gmail.com> wrote:
> > Hi
> >
> > I am running a full test on Windows.
> >
> > There is a single test in camel-aws that fails. I guess its related to
> > not being able to delete the file.
> > Will dig into this later when getting a bit of time. Either later
> > today or tomorrow morning.
> >
> > If anyone on Windows, then feel free to look into that failing test so
> > we can have it fixed before cutting the 2.11 release.
> >
> >
> > On Fri, Apr 5, 2013 at 12:32 PM, Claus Ibsen <cl...@gmail.com>
> wrote:
> >> Just a note to us that we should remember checkin the maven archetype
> >> for the blueprint.
> >> There may be a problem with 2x blueprint on the classpath when using
> camel:run
> >>
> >> On Fri, Apr 5, 2013 at 12:13 PM, Jan Matèrne (jhm) <ap...@materne.de>
> wrote:
> >>>> There is a new Apache SMX bundle in VOTE just now.
> >>>> Wonder if we should wait for this release so the Camel bundles can use
> >>>> these upgrades?
> >>>> Or maybe we want to get the 2.11 out sooner?
> >>>
> >>> I think there always will be a coming release and you should not try to
> >>> catch all of them.
> >>> You could upgrade with a 2.12 if necessary.
> >>>
> >>> Just my 2ct
> >>> Jan
> >>>
> >>
> >>
> >>
> >> --
> >> Claus Ibsen
> >> -----------------
> >> Red Hat, Inc.
> >> FuseSource is now part of Red Hat
> >> Email: cibsen@redhat.com
> >> Web: http://fusesource.com
> >> Twitter: davsclaus
> >> Blog: http://davsclaus.com
> >> Author of Camel in Action: http://www.manning.com/ibsen
> >
> >
> >
> > --
> > Claus Ibsen
> > -----------------
> > Red Hat, Inc.
> > FuseSource is now part of Red Hat
> > Email: cibsen@redhat.com
> > Web: http://fusesource.com
> > Twitter: davsclaus
> > Blog: http://davsclaus.com
> > Author of Camel in Action: http://www.manning.com/ibsen
>
>
>
> --
> Claus Ibsen
> -----------------
> Red Hat, Inc.
> FuseSource is now part of Red Hat
> Email: cibsen@redhat.com
> Web: http://fusesource.com
> Twitter: davsclaus
> Blog: http://davsclaus.com
> Author of Camel in Action: http://www.manning.com/ibsen
>
Re: [DISCUSS] - Moving towards Camel 2.11 release
Posted by Claus Ibsen <cl...@gmail.com>.
Hi
Okay so we have 2 issues
- a test in camel-aws fails on Windows.
- camel:run in blueprint does not work
I will work on the latter tomorrow morning.
And then look at the failing test on Windows (it indicate a problem
with not closing a file input stream, causing the file to be locked).
IMHO we should have these 2 fixed before we can cut the RC.
On Fri, Apr 5, 2013 at 4:09 PM, Claus Ibsen <cl...@gmail.com> wrote:
> Hi
>
> I am running a full test on Windows.
>
> There is a single test in camel-aws that fails. I guess its related to
> not being able to delete the file.
> Will dig into this later when getting a bit of time. Either later
> today or tomorrow morning.
>
> If anyone on Windows, then feel free to look into that failing test so
> we can have it fixed before cutting the 2.11 release.
>
>
> On Fri, Apr 5, 2013 at 12:32 PM, Claus Ibsen <cl...@gmail.com> wrote:
>> Just a note to us that we should remember checkin the maven archetype
>> for the blueprint.
>> There may be a problem with 2x blueprint on the classpath when using camel:run
>>
>> On Fri, Apr 5, 2013 at 12:13 PM, Jan Matèrne (jhm) <ap...@materne.de> wrote:
>>>> There is a new Apache SMX bundle in VOTE just now.
>>>> Wonder if we should wait for this release so the Camel bundles can use
>>>> these upgrades?
>>>> Or maybe we want to get the 2.11 out sooner?
>>>
>>> I think there always will be a coming release and you should not try to
>>> catch all of them.
>>> You could upgrade with a 2.12 if necessary.
>>>
>>> Just my 2ct
>>> Jan
>>>
>>
>>
>>
>> --
>> Claus Ibsen
>> -----------------
>> Red Hat, Inc.
>> FuseSource is now part of Red Hat
>> Email: cibsen@redhat.com
>> Web: http://fusesource.com
>> Twitter: davsclaus
>> Blog: http://davsclaus.com
>> Author of Camel in Action: http://www.manning.com/ibsen
>
>
>
> --
> Claus Ibsen
> -----------------
> Red Hat, Inc.
> FuseSource is now part of Red Hat
> Email: cibsen@redhat.com
> Web: http://fusesource.com
> Twitter: davsclaus
> Blog: http://davsclaus.com
> Author of Camel in Action: http://www.manning.com/ibsen
--
Claus Ibsen
-----------------
Red Hat, Inc.
FuseSource is now part of Red Hat
Email: cibsen@redhat.com
Web: http://fusesource.com
Twitter: davsclaus
Blog: http://davsclaus.com
Author of Camel in Action: http://www.manning.com/ibsen
Re: [DISCUSS] - Moving towards Camel 2.11 release
Posted by Claus Ibsen <cl...@gmail.com>.
Hi
I am running a full test on Windows.
There is a single test in camel-aws that fails. I guess its related to
not being able to delete the file.
Will dig into this later when getting a bit of time. Either later
today or tomorrow morning.
If anyone on Windows, then feel free to look into that failing test so
we can have it fixed before cutting the 2.11 release.
On Fri, Apr 5, 2013 at 12:32 PM, Claus Ibsen <cl...@gmail.com> wrote:
> Just a note to us that we should remember checkin the maven archetype
> for the blueprint.
> There may be a problem with 2x blueprint on the classpath when using camel:run
>
> On Fri, Apr 5, 2013 at 12:13 PM, Jan Matèrne (jhm) <ap...@materne.de> wrote:
>>> There is a new Apache SMX bundle in VOTE just now.
>>> Wonder if we should wait for this release so the Camel bundles can use
>>> these upgrades?
>>> Or maybe we want to get the 2.11 out sooner?
>>
>> I think there always will be a coming release and you should not try to
>> catch all of them.
>> You could upgrade with a 2.12 if necessary.
>>
>> Just my 2ct
>> Jan
>>
>
>
>
> --
> Claus Ibsen
> -----------------
> Red Hat, Inc.
> FuseSource is now part of Red Hat
> Email: cibsen@redhat.com
> Web: http://fusesource.com
> Twitter: davsclaus
> Blog: http://davsclaus.com
> Author of Camel in Action: http://www.manning.com/ibsen
--
Claus Ibsen
-----------------
Red Hat, Inc.
FuseSource is now part of Red Hat
Email: cibsen@redhat.com
Web: http://fusesource.com
Twitter: davsclaus
Blog: http://davsclaus.com
Author of Camel in Action: http://www.manning.com/ibsen
Re: [DISCUSS] - Moving towards Camel 2.11 release
Posted by Claus Ibsen <cl...@gmail.com>.
Just a note to us that we should remember checkin the maven archetype
for the blueprint.
There may be a problem with 2x blueprint on the classpath when using camel:run
On Fri, Apr 5, 2013 at 12:13 PM, Jan Matèrne (jhm) <ap...@materne.de> wrote:
>> There is a new Apache SMX bundle in VOTE just now.
>> Wonder if we should wait for this release so the Camel bundles can use
>> these upgrades?
>> Or maybe we want to get the 2.11 out sooner?
>
> I think there always will be a coming release and you should not try to
> catch all of them.
> You could upgrade with a 2.12 if necessary.
>
> Just my 2ct
> Jan
>
--
Claus Ibsen
-----------------
Red Hat, Inc.
FuseSource is now part of Red Hat
Email: cibsen@redhat.com
Web: http://fusesource.com
Twitter: davsclaus
Blog: http://davsclaus.com
Author of Camel in Action: http://www.manning.com/ibsen
AW: [DISCUSS] - Moving towards Camel 2.11 release
Posted by "Jan Matèrne (jhm)" <ap...@materne.de>.
> There is a new Apache SMX bundle in VOTE just now.
> Wonder if we should wait for this release so the Camel bundles can use
> these upgrades?
> Or maybe we want to get the 2.11 out sooner?
I think there always will be a coming release and you should not try to
catch all of them.
You could upgrade with a 2.12 if necessary.
Just my 2ct
Jan
Re: [DISCUSS] - Moving towards Camel 2.11 release
Posted by Claus Ibsen <cl...@gmail.com>.
Hi
There is a new Apache SMX bundle in VOTE just now.
Wonder if we should wait for this release so the Camel bundles can use
these upgrades?
Or maybe we want to get the 2.11 out sooner?
On Fri, Apr 5, 2013 at 10:15 AM, Babak Vahdat
<ba...@swissonline.ch> wrote:
> Hi Christian,
>
> I assume building the camel-bindy module on your Mac will fail like for me
> as you have german locale the same as me (this is just a guess of mine).
> So I raised the following ticket to get this fixed today in case you take
> over the release tomorrow.
>
> https://issues.apache.org/jira/browse/CAMEL-6241
>
> Babak
>
>
> Christian Mueller wrote
>> +1
>> Hadrian, I could do the release too. I have free cycles starting at
>> Saturday.
>>
>> Best,
>> Christian
>>
>>
>> On Thu, Apr 4, 2013 at 4:20 PM, Claus Ibsen <
>
>> claus.ibsen@
>
>> > wrote:
>>
>>> Hi
>>>
>>> I am currently working on making the Camel Karaf commands move
>>> powerful. That needs a little bit of more love today and tomorrow. Its
>>> already coming out nicely with new tracing and profiling you can
>>> enable on the fly. That can give our users a little insight what is
>>> happening.
>>>
>>> For example if you run
>>>
>>> watch camel:route-profile *
>>>
>>> You get a live update of route profiles.
>>>
>>> Here is a little "screen shot".
>>>
>>> We have 2 routes in the same context. Route zzz and aaa.
>>> The routes is ordered how they were started, as for example you may
>>> flow messages from zzz -> aaa.
>>>
>>> Yes I used names zzz and aaa, to test that they are listed correctly.
>>> eg zzz starts before aaa.
>>>
>>>
>>>
>>> Profile
>>> Camel Context: blueprintContext
>>> Id Count Last (ms) Delta (ms)
>>> Mean (ms) Min (ms) Max (ms) Self (ms)
>>> [zzz ] [ 113] [ 1] [ -1] [
>>> 1] [ 0] [ 11] [ ]
>>> [ setBody1 ] [ 113] [ 0] [ 0] [
>>> 0] [ 0] [ 4] [ 36]
>>> [ to1 ] [ 113] [ 0] [ 0] [
>>> 0] [ 0] [ 1] [ 21]
>>> [aaa ] [ 113] [ 0] [ -1] [
>>> 0] [ 0] [ 1] [ ]
>>> [ log1 ] [ 113] [ 0] [ 0] [
>>> 0] [ 0] [ 1] [ 54]
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> I would suggest that we close down early next week and focus on cutting a
>>> RC.
>>>
>>> Hadrian do you have time to work on a release next week?
>>>
>>> --
>>> Claus Ibsen
>>> -----------------
>>> Red Hat, Inc.
>>> FuseSource is now part of Red Hat
>>> Email:
>
>> cibsen@
>
>>> Web: http://fusesource.com
>>> Twitter: davsclaus
>>> Blog: http://davsclaus.com
>>> Author of Camel in Action: http://www.manning.com/ibsen
>>>
>
>
>
>
>
> --
> View this message in context: http://camel.465427.n5.nabble.com/DISCUSS-Moving-towards-Camel-2-11-release-tp5725088p5730383.html
> Sent from the Camel Development mailing list archive at Nabble.com.
--
Claus Ibsen
-----------------
Red Hat, Inc.
FuseSource is now part of Red Hat
Email: cibsen@redhat.com
Web: http://fusesource.com
Twitter: davsclaus
Blog: http://davsclaus.com
Author of Camel in Action: http://www.manning.com/ibsen
Re: [DISCUSS] - Moving towards Camel 2.11 release
Posted by Christian Müller <ch...@gmail.com>.
Hi Babak!
Thanks for fixing it. But I use en_US as locale ;-)
cmueller$ mvn -v
Apache Maven 3.0.5 (r01de14724cdef164cd33c7c8c2fe155faf9602da; 2013-02-19
14:51:28+0100)
Maven home: /Applications/apache-maven-3.0.5
Java version: 1.6.0_43, vendor: Apple Inc.
Java home:
/Library/Java/JavaVirtualMachines/1.6.0_43-b01-447.jdk/Contents/Home
Default locale: en_US, platform encoding: MacRoman
OS name: "mac os x", version: "10.8.3", arch: "x86_64", family: "mac"
Best,
Christian
On Fri, Apr 5, 2013 at 10:15 AM, Babak Vahdat
<ba...@swissonline.ch>wrote:
> Hi Christian,
>
> I assume building the camel-bindy module on your Mac will fail like for me
> as you have german locale the same as me (this is just a guess of mine).
> So I raised the following ticket to get this fixed today in case you take
> over the release tomorrow.
>
> https://issues.apache.org/jira/browse/CAMEL-6241
>
> Babak
>
>
> Christian Mueller wrote
> > +1
> > Hadrian, I could do the release too. I have free cycles starting at
> > Saturday.
> >
> > Best,
> > Christian
> >
> >
> > On Thu, Apr 4, 2013 at 4:20 PM, Claus Ibsen <
>
> > claus.ibsen@
>
> > > wrote:
> >
> >> Hi
> >>
> >> I am currently working on making the Camel Karaf commands move
> >> powerful. That needs a little bit of more love today and tomorrow. Its
> >> already coming out nicely with new tracing and profiling you can
> >> enable on the fly. That can give our users a little insight what is
> >> happening.
> >>
> >> For example if you run
> >>
> >> watch camel:route-profile *
> >>
> >> You get a live update of route profiles.
> >>
> >> Here is a little "screen shot".
> >>
> >> We have 2 routes in the same context. Route zzz and aaa.
> >> The routes is ordered how they were started, as for example you may
> >> flow messages from zzz -> aaa.
> >>
> >> Yes I used names zzz and aaa, to test that they are listed correctly.
> >> eg zzz starts before aaa.
> >>
> >>
> >>
> >> Profile
> >> Camel Context: blueprintContext
> >> Id Count Last (ms) Delta (ms)
> >> Mean (ms) Min (ms) Max (ms) Self (ms)
> >> [zzz ] [ 113] [ 1] [ -1] [
> >> 1] [ 0] [ 11] [ ]
> >> [ setBody1 ] [ 113] [ 0] [ 0] [
> >> 0] [ 0] [ 4] [ 36]
> >> [ to1 ] [ 113] [ 0] [ 0] [
> >> 0] [ 0] [ 1] [ 21]
> >> [aaa ] [ 113] [ 0] [ -1] [
> >> 0] [ 0] [ 1] [ ]
> >> [ log1 ] [ 113] [ 0] [ 0] [
> >> 0] [ 0] [ 1] [ 54]
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >> I would suggest that we close down early next week and focus on cutting
> a
> >> RC.
> >>
> >> Hadrian do you have time to work on a release next week?
> >>
> >> --
> >> Claus Ibsen
> >> -----------------
> >> Red Hat, Inc.
> >> FuseSource is now part of Red Hat
> >> Email:
>
> > cibsen@
>
> >> Web: http://fusesource.com
> >> Twitter: davsclaus
> >> Blog: http://davsclaus.com
> >> Author of Camel in Action: http://www.manning.com/ibsen
> >>
>
>
>
>
>
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/DISCUSS-Moving-towards-Camel-2-11-release-tp5725088p5730383.html
> Sent from the Camel Development mailing list archive at Nabble.com.
>
Re: [DISCUSS] - Moving towards Camel 2.11 release
Posted by Babak Vahdat <ba...@swissonline.ch>.
Hi Christian,
I assume building the camel-bindy module on your Mac will fail like for me
as you have german locale the same as me (this is just a guess of mine).
So I raised the following ticket to get this fixed today in case you take
over the release tomorrow.
https://issues.apache.org/jira/browse/CAMEL-6241
Babak
Christian Mueller wrote
> +1
> Hadrian, I could do the release too. I have free cycles starting at
> Saturday.
>
> Best,
> Christian
>
>
> On Thu, Apr 4, 2013 at 4:20 PM, Claus Ibsen <
> claus.ibsen@
> > wrote:
>
>> Hi
>>
>> I am currently working on making the Camel Karaf commands move
>> powerful. That needs a little bit of more love today and tomorrow. Its
>> already coming out nicely with new tracing and profiling you can
>> enable on the fly. That can give our users a little insight what is
>> happening.
>>
>> For example if you run
>>
>> watch camel:route-profile *
>>
>> You get a live update of route profiles.
>>
>> Here is a little "screen shot".
>>
>> We have 2 routes in the same context. Route zzz and aaa.
>> The routes is ordered how they were started, as for example you may
>> flow messages from zzz -> aaa.
>>
>> Yes I used names zzz and aaa, to test that they are listed correctly.
>> eg zzz starts before aaa.
>>
>>
>>
>> Profile
>> Camel Context: blueprintContext
>> Id Count Last (ms) Delta (ms)
>> Mean (ms) Min (ms) Max (ms) Self (ms)
>> [zzz ] [ 113] [ 1] [ -1] [
>> 1] [ 0] [ 11] [ ]
>> [ setBody1 ] [ 113] [ 0] [ 0] [
>> 0] [ 0] [ 4] [ 36]
>> [ to1 ] [ 113] [ 0] [ 0] [
>> 0] [ 0] [ 1] [ 21]
>> [aaa ] [ 113] [ 0] [ -1] [
>> 0] [ 0] [ 1] [ ]
>> [ log1 ] [ 113] [ 0] [ 0] [
>> 0] [ 0] [ 1] [ 54]
>>
>>
>>
>>
>>
>>
>>
>> I would suggest that we close down early next week and focus on cutting a
>> RC.
>>
>> Hadrian do you have time to work on a release next week?
>>
>> --
>> Claus Ibsen
>> -----------------
>> Red Hat, Inc.
>> FuseSource is now part of Red Hat
>> Email:
> cibsen@
>> Web: http://fusesource.com
>> Twitter: davsclaus
>> Blog: http://davsclaus.com
>> Author of Camel in Action: http://www.manning.com/ibsen
>>
--
View this message in context: http://camel.465427.n5.nabble.com/DISCUSS-Moving-towards-Camel-2-11-release-tp5725088p5730383.html
Sent from the Camel Development mailing list archive at Nabble.com.
Re: [DISCUSS] - Moving towards Camel 2.11 release
Posted by Christian Müller <ch...@gmail.com>.
+1
Hadrian, I could do the release too. I have free cycles starting at
Saturday.
Best,
Christian
On Thu, Apr 4, 2013 at 4:20 PM, Claus Ibsen <cl...@gmail.com> wrote:
> Hi
>
> I am currently working on making the Camel Karaf commands move
> powerful. That needs a little bit of more love today and tomorrow. Its
> already coming out nicely with new tracing and profiling you can
> enable on the fly. That can give our users a little insight what is
> happening.
>
> For example if you run
>
> watch camel:route-profile *
>
> You get a live update of route profiles.
>
> Here is a little "screen shot".
>
> We have 2 routes in the same context. Route zzz and aaa.
> The routes is ordered how they were started, as for example you may
> flow messages from zzz -> aaa.
>
> Yes I used names zzz and aaa, to test that they are listed correctly.
> eg zzz starts before aaa.
>
>
>
> Profile
> Camel Context: blueprintContext
> Id Count Last (ms) Delta (ms)
> Mean (ms) Min (ms) Max (ms) Self (ms)
> [zzz ] [ 113] [ 1] [ -1] [
> 1] [ 0] [ 11] [ ]
> [ setBody1 ] [ 113] [ 0] [ 0] [
> 0] [ 0] [ 4] [ 36]
> [ to1 ] [ 113] [ 0] [ 0] [
> 0] [ 0] [ 1] [ 21]
> [aaa ] [ 113] [ 0] [ -1] [
> 0] [ 0] [ 1] [ ]
> [ log1 ] [ 113] [ 0] [ 0] [
> 0] [ 0] [ 1] [ 54]
>
>
>
>
>
>
>
> I would suggest that we close down early next week and focus on cutting a
> RC.
>
> Hadrian do you have time to work on a release next week?
>
> --
> Claus Ibsen
> -----------------
> Red Hat, Inc.
> FuseSource is now part of Red Hat
> Email: cibsen@redhat.com
> Web: http://fusesource.com
> Twitter: davsclaus
> Blog: http://davsclaus.com
> Author of Camel in Action: http://www.manning.com/ibsen
>
Re: [DISCUSS] - Moving towards Camel 2.11 release
Posted by Claus Ibsen <cl...@gmail.com>.
Hi
I am currently working on making the Camel Karaf commands move
powerful. That needs a little bit of more love today and tomorrow. Its
already coming out nicely with new tracing and profiling you can
enable on the fly. That can give our users a little insight what is
happening.
For example if you run
watch camel:route-profile *
You get a live update of route profiles.
Here is a little "screen shot".
We have 2 routes in the same context. Route zzz and aaa.
The routes is ordered how they were started, as for example you may
flow messages from zzz -> aaa.
Yes I used names zzz and aaa, to test that they are listed correctly.
eg zzz starts before aaa.
Profile
Camel Context: blueprintContext
Id Count Last (ms) Delta (ms)
Mean (ms) Min (ms) Max (ms) Self (ms)
[zzz ] [ 113] [ 1] [ -1] [
1] [ 0] [ 11] [ ]
[ setBody1 ] [ 113] [ 0] [ 0] [
0] [ 0] [ 4] [ 36]
[ to1 ] [ 113] [ 0] [ 0] [
0] [ 0] [ 1] [ 21]
[aaa ] [ 113] [ 0] [ -1] [
0] [ 0] [ 1] [ ]
[ log1 ] [ 113] [ 0] [ 0] [
0] [ 0] [ 1] [ 54]
I would suggest that we close down early next week and focus on cutting a RC.
Hadrian do you have time to work on a release next week?
--
Claus Ibsen
-----------------
Red Hat, Inc.
FuseSource is now part of Red Hat
Email: cibsen@redhat.com
Web: http://fusesource.com
Twitter: davsclaus
Blog: http://davsclaus.com
Author of Camel in Action: http://www.manning.com/ibsen
Re: [DISCUSS] - Moving towards Camel 2.11 release
Posted by Hadrian Zbarcea <hz...@gmail.com>.
I think there is a problem with camel-bindy as well. I am looking into
it today.
Hadrian
On 04/02/2013 12:37 PM, Christian Müller wrote:
> I think it would be good if we could include CAMEL-6218 into Camel 2.11.0.
> May an ActiveMQ expert could have a look into it?
>
> Best,
> Christian
>
>
> On Tue, Apr 2, 2013 at 5:11 PM, AlanFoster <al...@alanfoster.me> wrote:
>
>> Hi all,
>>
>> Just posting to let you know that Christian Müller mentioned the
>> possibility
>> of CAMEL-6218 being included in the Camel 2.11 release
>> (https://issues.apache.org/jira/browse/CAMEL-6218).
>>
>> There has been a lot of improvements for using the InOut MEP with the JMS
>> component, so it seems fitting to include such as fix in Camel 2.11
>>
>> Alan
>>
>>
>>
>> --
>> View this message in context:
>> http://camel.465427.n5.nabble.com/DISCUSS-Moving-towards-Camel-2-11-release-tp5725088p5730225.html
>> Sent from the Camel Development mailing list archive at Nabble.com.
>>
>
Re: [DISCUSS] - Moving towards Camel 2.11 release
Posted by Raul Kripalani <ra...@evosent.com>.
I'll take a stab at it this evening!
Regards,
*Raúl Kripalani*
Enterprise Architect, Open Source Integration specialist, Program
Manager | Apache
Camel Committer
http://about.me/raulkripalani | http://www.linkedin.com/in/raulkripalani
http://blog.raulkr.net | twitter: @raulvk
On Tue, Apr 2, 2013 at 5:37 PM, Christian Müller <
christian.mueller@gmail.com> wrote:
> I think it would be good if we could include CAMEL-6218 into Camel 2.11.0.
> May an ActiveMQ expert could have a look into it?
>
> Best,
> Christian
>
>
Re: [DISCUSS] - Moving towards Camel 2.11 release
Posted by Christian Müller <ch...@gmail.com>.
I think it would be good if we could include CAMEL-6218 into Camel 2.11.0.
May an ActiveMQ expert could have a look into it?
Best,
Christian
On Tue, Apr 2, 2013 at 5:11 PM, AlanFoster <al...@alanfoster.me> wrote:
> Hi all,
>
> Just posting to let you know that Christian Müller mentioned the
> possibility
> of CAMEL-6218 being included in the Camel 2.11 release
> (https://issues.apache.org/jira/browse/CAMEL-6218).
>
> There has been a lot of improvements for using the InOut MEP with the JMS
> component, so it seems fitting to include such as fix in Camel 2.11
>
> Alan
>
>
>
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/DISCUSS-Moving-towards-Camel-2-11-release-tp5725088p5730225.html
> Sent from the Camel Development mailing list archive at Nabble.com.
>
Re: [DISCUSS] - Moving towards Camel 2.11 release
Posted by AlanFoster <al...@alanfoster.me>.
Hi all,
Just posting to let you know that Christian Müller mentioned the possibility
of CAMEL-6218 being included in the Camel 2.11 release
(https://issues.apache.org/jira/browse/CAMEL-6218).
There has been a lot of improvements for using the InOut MEP with the JMS
component, so it seems fitting to include such as fix in Camel 2.11
Alan
--
View this message in context: http://camel.465427.n5.nabble.com/DISCUSS-Moving-towards-Camel-2-11-release-tp5725088p5730225.html
Sent from the Camel Development mailing list archive at Nabble.com.