You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by Willem jiang <wi...@gmail.com> on 2013/08/27 11:52:02 UTC

Camel 2.12.0 release

Hi,   

I'm planing cut the Camel 2.12.0 release 12 hours later (About 27 August 2013, 10 PM  GMT).
Please don't commit any code at that time and make sure the code you commit don't break any thing if you had to commit the code today.

Thanks,  

--  
Willem Jiang

Red Hat, Inc.
Web: http://www.redhat.com
Blog: http://willemjiang.blogspot.com (http://willemjiang.blogspot.com/) (English)
          http://jnn.iteye.com (http://jnn.javaeye.com/) (Chinese)
Twitter: willemjiang  
Weibo: 姜宁willem






Re: Camel 2.12.0 release

Posted by Christian Müller <ch...@gmail.com>.
+1

Best,
Christian
-----------------

Software Integration Specialist

Apache Camel committer: https://camel.apache.org/team
V.P. Apache Camel: https://www.apache.org/foundation/
Apache Member: https://www.apache.org/foundation/members.html

https://www.linkedin.com/pub/christian-mueller/11/551/642


On Tue, Aug 27, 2013 at 2:11 PM, Claus Ibsen <cl...@gmail.com> wrote:

> Hi
>
> Yeah AMQ 5.9 is not so far away. It requires Camel 2.12 and hence
> would need this release.
>
> We could start a talk on ActiveMQ @dev about the 5.9 release. As that
> would be required for a new SMX release also so its up to date with
> latest Karaf / AMQ / Camel / CXF etc.
>
>
>
>
> On Tue, Aug 27, 2013 at 1:53 PM, Christian Schneider
> <ch...@die-schneider.net> wrote:
> > Sorry for not checking this more thoroughly.
> > Yes. The camel feature file does not reference activemq.
> >
> > I just tested my camel tutorial example with camel 2.11.1 and activemq
> > 5.7.0. The problem I face there is that activemq 5.7.0 does not work on
> > karaf 2.3.x
> > because it requires a blueprint version <1.0.0. So the problem is still
> > there but it is not related to camel.
> >
> > On activemq 5.8 on the other hand the whole broker creation and blueprint
> > support does not work.
> >
> > So all fine with the camel release. The problem is on activemq side.
> >
> > Do you know when activemq 5.9 is scheduled?
> >
> > Christian
> >
> >
> >
> > On 27.08.2013 13:16, Claus Ibsen wrote:
> >>
> >> I cannot see how this related to Apache Camel?
> >>
> >> At Apache Camel we do not have any OSGi imports/features for Apache
> >> ActiveMQ.
> >> Its "the other way around". ActiveMQ has a Camel module, and its own
> >> feature files.
> >>
> >> And the OSGi problems in AMQ 5.8.0 has been fixed on trunk and will be
> >> in the upcoming 5.9 release.
> >> And AMQ 5.9.0 will use the Apache Camel 2.12 release.
> >>
> >>
> >>
> >> On Tue, Aug 27, 2013 at 12:54 PM, Christian Schneider
> >> <ch...@die-schneider.net> wrote:
> >>>
> >>> We currently have some issues with ActiveMQ 8 on OSGi.
> >>> Would it make sense to switch back to ActiveMQ 7 in the feature and
> >>> possibly
> >>> for imports for 2.12.0?
> >>>
> >>> Christian
> >>>
> >>>
> >>>
> >>> On 27.08.2013 11:52, Willem jiang wrote:
> >>>>
> >>>> Hi,
> >>>>
> >>>> I'm planing cut the Camel 2.12.0 release 12 hours later (About 27
> August
> >>>> 2013, 10 PM  GMT).
> >>>> Please don't commit any code at that time and make sure the code you
> >>>> commit don't break any thing if you had to commit the code today.
> >>>>
> >>>> Thanks,
> >>>>
> >>>> --
> >>>> Willem Jiang
> >>>>
> >>>> Red Hat, Inc.
> >>>> Web: http://www.redhat.com
> >>>> Blog: http://willemjiang.blogspot.com (
> http://willemjiang.blogspot.com/)
> >>>> (English)
> >>>>             http://jnn.iteye.com (http://jnn.javaeye.com/) (Chinese)
> >>>> Twitter: willemjiang
> >>>> Weibo: 姜宁willem
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>
> >>>
> >>> --
> >>> Christian Schneider
> >>> http://www.liquid-reality.de
> >>>
> >>> Open Source Architect
> >>> http://www.talend.com
> >>>
> >>
> >>
> >
> >
> > --
> > Christian Schneider
> > http://www.liquid-reality.de
> >
> > Open Source Architect
> > http://www.talend.com
> >
>
>
>
> --
> Claus Ibsen
> -----------------
> Red Hat, Inc.
> Email: cibsen@redhat.com
> Twitter: davsclaus
> Blog: http://davsclaus.com
> Author of Camel in Action: http://www.manning.com/ibsen
>

Re: Camel 2.12.0 release

Posted by Claus Ibsen <cl...@gmail.com>.
Hi

Yeah AMQ 5.9 is not so far away. It requires Camel 2.12 and hence
would need this release.

We could start a talk on ActiveMQ @dev about the 5.9 release. As that
would be required for a new SMX release also so its up to date with
latest Karaf / AMQ / Camel / CXF etc.




On Tue, Aug 27, 2013 at 1:53 PM, Christian Schneider
<ch...@die-schneider.net> wrote:
> Sorry for not checking this more thoroughly.
> Yes. The camel feature file does not reference activemq.
>
> I just tested my camel tutorial example with camel 2.11.1 and activemq
> 5.7.0. The problem I face there is that activemq 5.7.0 does not work on
> karaf 2.3.x
> because it requires a blueprint version <1.0.0. So the problem is still
> there but it is not related to camel.
>
> On activemq 5.8 on the other hand the whole broker creation and blueprint
> support does not work.
>
> So all fine with the camel release. The problem is on activemq side.
>
> Do you know when activemq 5.9 is scheduled?
>
> Christian
>
>
>
> On 27.08.2013 13:16, Claus Ibsen wrote:
>>
>> I cannot see how this related to Apache Camel?
>>
>> At Apache Camel we do not have any OSGi imports/features for Apache
>> ActiveMQ.
>> Its "the other way around". ActiveMQ has a Camel module, and its own
>> feature files.
>>
>> And the OSGi problems in AMQ 5.8.0 has been fixed on trunk and will be
>> in the upcoming 5.9 release.
>> And AMQ 5.9.0 will use the Apache Camel 2.12 release.
>>
>>
>>
>> On Tue, Aug 27, 2013 at 12:54 PM, Christian Schneider
>> <ch...@die-schneider.net> wrote:
>>>
>>> We currently have some issues with ActiveMQ 8 on OSGi.
>>> Would it make sense to switch back to ActiveMQ 7 in the feature and
>>> possibly
>>> for imports for 2.12.0?
>>>
>>> Christian
>>>
>>>
>>>
>>> On 27.08.2013 11:52, Willem jiang wrote:
>>>>
>>>> Hi,
>>>>
>>>> I'm planing cut the Camel 2.12.0 release 12 hours later (About 27 August
>>>> 2013, 10 PM  GMT).
>>>> Please don't commit any code at that time and make sure the code you
>>>> commit don't break any thing if you had to commit the code today.
>>>>
>>>> Thanks,
>>>>
>>>> --
>>>> Willem Jiang
>>>>
>>>> Red Hat, Inc.
>>>> Web: http://www.redhat.com
>>>> Blog: http://willemjiang.blogspot.com (http://willemjiang.blogspot.com/)
>>>> (English)
>>>>             http://jnn.iteye.com (http://jnn.javaeye.com/) (Chinese)
>>>> Twitter: willemjiang
>>>> Weibo: 姜宁willem
>>>>
>>>>
>>>>
>>>>
>>>>
>>>
>>> --
>>> Christian Schneider
>>> http://www.liquid-reality.de
>>>
>>> Open Source Architect
>>> http://www.talend.com
>>>
>>
>>
>
>
> --
> Christian Schneider
> http://www.liquid-reality.de
>
> Open Source Architect
> http://www.talend.com
>



-- 
Claus Ibsen
-----------------
Red Hat, Inc.
Email: cibsen@redhat.com
Twitter: davsclaus
Blog: http://davsclaus.com
Author of Camel in Action: http://www.manning.com/ibsen

Re: Camel 2.12.0 release

Posted by Christian Schneider <ch...@die-schneider.net>.
Sorry for not checking this more thoroughly.
Yes. The camel feature file does not reference activemq.

I just tested my camel tutorial example with camel 2.11.1 and activemq 
5.7.0. The problem I face there is that activemq 5.7.0 does not work on 
karaf 2.3.x
because it requires a blueprint version <1.0.0. So the problem is still 
there but it is not related to camel.

On activemq 5.8 on the other hand the whole broker creation and 
blueprint support does not work.

So all fine with the camel release. The problem is on activemq side.

Do you know when activemq 5.9 is scheduled?

Christian


On 27.08.2013 13:16, Claus Ibsen wrote:
> I cannot see how this related to Apache Camel?
>
> At Apache Camel we do not have any OSGi imports/features for Apache ActiveMQ.
> Its "the other way around". ActiveMQ has a Camel module, and its own
> feature files.
>
> And the OSGi problems in AMQ 5.8.0 has been fixed on trunk and will be
> in the upcoming 5.9 release.
> And AMQ 5.9.0 will use the Apache Camel 2.12 release.
>
>
>
> On Tue, Aug 27, 2013 at 12:54 PM, Christian Schneider
> <ch...@die-schneider.net> wrote:
>> We currently have some issues with ActiveMQ 8 on OSGi.
>> Would it make sense to switch back to ActiveMQ 7 in the feature and possibly
>> for imports for 2.12.0?
>>
>> Christian
>>
>>
>>
>> On 27.08.2013 11:52, Willem jiang wrote:
>>> Hi,
>>>
>>> I'm planing cut the Camel 2.12.0 release 12 hours later (About 27 August
>>> 2013, 10 PM  GMT).
>>> Please don't commit any code at that time and make sure the code you
>>> commit don't break any thing if you had to commit the code today.
>>>
>>> Thanks,
>>>
>>> --
>>> Willem Jiang
>>>
>>> Red Hat, Inc.
>>> Web: http://www.redhat.com
>>> Blog: http://willemjiang.blogspot.com (http://willemjiang.blogspot.com/)
>>> (English)
>>>             http://jnn.iteye.com (http://jnn.javaeye.com/) (Chinese)
>>> Twitter: willemjiang
>>> Weibo: 姜宁willem
>>>
>>>
>>>
>>>
>>>
>>
>> --
>> Christian Schneider
>> http://www.liquid-reality.de
>>
>> Open Source Architect
>> http://www.talend.com
>>
>
>


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

Open Source Architect
http://www.talend.com


Re: Camel 2.12.0 release

Posted by Claus Ibsen <cl...@gmail.com>.
I cannot see how this related to Apache Camel?

At Apache Camel we do not have any OSGi imports/features for Apache ActiveMQ.
Its "the other way around". ActiveMQ has a Camel module, and its own
feature files.

And the OSGi problems in AMQ 5.8.0 has been fixed on trunk and will be
in the upcoming 5.9 release.
And AMQ 5.9.0 will use the Apache Camel 2.12 release.



On Tue, Aug 27, 2013 at 12:54 PM, Christian Schneider
<ch...@die-schneider.net> wrote:
> We currently have some issues with ActiveMQ 8 on OSGi.
> Would it make sense to switch back to ActiveMQ 7 in the feature and possibly
> for imports for 2.12.0?
>
> Christian
>
>
>
> On 27.08.2013 11:52, Willem jiang wrote:
>>
>> Hi,
>>
>> I'm planing cut the Camel 2.12.0 release 12 hours later (About 27 August
>> 2013, 10 PM  GMT).
>> Please don't commit any code at that time and make sure the code you
>> commit don't break any thing if you had to commit the code today.
>>
>> Thanks,
>>
>> --
>> Willem Jiang
>>
>> Red Hat, Inc.
>> Web: http://www.redhat.com
>> Blog: http://willemjiang.blogspot.com (http://willemjiang.blogspot.com/)
>> (English)
>>            http://jnn.iteye.com (http://jnn.javaeye.com/) (Chinese)
>> Twitter: willemjiang
>> Weibo: 姜宁willem
>>
>>
>>
>>
>>
>
>
> --
> Christian Schneider
> http://www.liquid-reality.de
>
> Open Source Architect
> http://www.talend.com
>



-- 
Claus Ibsen
-----------------
Red Hat, Inc.
Email: cibsen@redhat.com
Twitter: davsclaus
Blog: http://davsclaus.com
Author of Camel in Action: http://www.manning.com/ibsen

Re: Camel 2.12.0 release

Posted by Christian Schneider <ch...@die-schneider.net>.
We currently have some issues with ActiveMQ 8 on OSGi.
Would it make sense to switch back to ActiveMQ 7 in the feature and 
possibly for imports for 2.12.0?

Christian


On 27.08.2013 11:52, Willem jiang wrote:
> Hi,
>
> I'm planing cut the Camel 2.12.0 release 12 hours later (About 27 August 2013, 10 PM  GMT).
> Please don't commit any code at that time and make sure the code you commit don't break any thing if you had to commit the code today.
>
> Thanks,
>
> --
> Willem Jiang
>
> Red Hat, Inc.
> Web: http://www.redhat.com
> Blog: http://willemjiang.blogspot.com (http://willemjiang.blogspot.com/) (English)
>            http://jnn.iteye.com (http://jnn.javaeye.com/) (Chinese)
> Twitter: willemjiang
> Weibo: 姜宁willem
>
>
>
>
>


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

Open Source Architect
http://www.talend.com


Re: Camel 2.12.0 release

Posted by Claus Ibsen <cl...@gmail.com>.
Hi

There is an issue with spi-annotations we need to sort before we can
cut a release.
I posted a mail on @dev on an existing thread about this.

On Tue, Aug 27, 2013 at 12:14 PM, Claus Ibsen <cl...@gmail.com> wrote:
> Hi
>
> Sounds good. There is a few new documents that needs documentation but
> I have moved them to 2.12.1, as we may not get the docs ready in time.
> And they can be added later.
>
> One of the new components is in camel-extra and hence okay for it to
> wait post 2.12 release.
>
>
>
> On Tue, Aug 27, 2013 at 11:52 AM, Willem jiang <wi...@gmail.com> wrote:
>> Hi,
>>
>> I'm planing cut the Camel 2.12.0 release 12 hours later (About 27 August 2013, 10 PM  GMT).
>> Please don't commit any code at that time and make sure the code you commit don't break any thing if you had to commit the code today.
>>
>> Thanks,
>>
>> --
>> Willem Jiang
>>
>> Red Hat, Inc.
>> Web: http://www.redhat.com
>> Blog: http://willemjiang.blogspot.com (http://willemjiang.blogspot.com/) (English)
>>           http://jnn.iteye.com (http://jnn.javaeye.com/) (Chinese)
>> Twitter: willemjiang
>> Weibo: 姜宁willem
>>
>>
>>
>>
>>
>
>
>
> --
> Claus Ibsen
> -----------------
> Red Hat, Inc.
> Email: cibsen@redhat.com
> Twitter: davsclaus
> Blog: http://davsclaus.com
> Author of Camel in Action: http://www.manning.com/ibsen



-- 
Claus Ibsen
-----------------
Red Hat, Inc.
Email: cibsen@redhat.com
Twitter: davsclaus
Blog: http://davsclaus.com
Author of Camel in Action: http://www.manning.com/ibsen

Re: Camel 2.12.0 release

Posted by Claus Ibsen <cl...@gmail.com>.
Hi

Sounds good. There is a few new documents that needs documentation but
I have moved them to 2.12.1, as we may not get the docs ready in time.
And they can be added later.

One of the new components is in camel-extra and hence okay for it to
wait post 2.12 release.



On Tue, Aug 27, 2013 at 11:52 AM, Willem jiang <wi...@gmail.com> wrote:
> Hi,
>
> I'm planing cut the Camel 2.12.0 release 12 hours later (About 27 August 2013, 10 PM  GMT).
> Please don't commit any code at that time and make sure the code you commit don't break any thing if you had to commit the code today.
>
> Thanks,
>
> --
> Willem Jiang
>
> Red Hat, Inc.
> Web: http://www.redhat.com
> Blog: http://willemjiang.blogspot.com (http://willemjiang.blogspot.com/) (English)
>           http://jnn.iteye.com (http://jnn.javaeye.com/) (Chinese)
> Twitter: willemjiang
> Weibo: 姜宁willem
>
>
>
>
>



-- 
Claus Ibsen
-----------------
Red Hat, Inc.
Email: cibsen@redhat.com
Twitter: davsclaus
Blog: http://davsclaus.com
Author of Camel in Action: http://www.manning.com/ibsen