You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by Omar Al-Safi <om...@oalsafi.com> on 2020/05/04 07:52:44 UTC
Re: [ROADMAP] - Apache Camel 3.3
+1
On Thu, Apr 30, 2020 at 9:59 PM Gregor Zurowski <gr...@list.zurowski.org>
wrote:
> +1
>
>
> On Thu, Apr 30, 2020, 5:19 PM Claus Ibsen <cl...@gmail.com> wrote:
>
> > Hi
> >
> > Just to get attention to this again. I would be good to finish up the
> > bits we can make and get Camel 3.3 timeboxed for release.
> >
> > So I suggest we by end of next week (friday) cut the RC. Then we can
> > get the release out here in start of May.
> > And then the 3.4 LTS release out in June / start of July (at latest).
> >
> > Any thoughts?
> >
> > On Wed, Apr 15, 2020 at 7:28 AM Claus Ibsen <cl...@gmail.com>
> wrote:
> > >
> > > Hi
> > >
> > > Lets keep the momentum going and release a new 3.x version next month.
> > > And lets aim for 3 weeks time. So if we can get Camel 3.3 released in
> > > start of / mid May 2020, then that would be great.
> > >
> > > Here are some of the areas to work on and see if we can get
> > > implemented and also the stuff already done.
> > >
> > > 1) Reflection free *DONE*
> > > We have continued the work to make Camel use less reflections and have
> > > now fixed the remainder bits in Rest DSL and Circuit Breakers.
> > > And there were some data formats that wasnt entirely fixed either.
> > >
> > > 2) Reflection free custom POJOs *DONE*
> > > We can now use @Configurer on custom POJOs and with our maven tool
> > > generate source code to configure without reflection
> > >
> > > 3) JAXB free *DONE*
> > > There were a few spots left to remove JAXB from the classpath when its
> > > not needed. Now Rest DSL is also free when you do not use XML
> > > bindings.
> > > And also remove JAXB from maven pom etc.
> > >
> > > 4) Bugs reported about Camel 3.2 *DONE*
> > > We have fixed the problems reported with Camel 3.2 such as install on
> > > karaf, or the endpoint-dsl not support property placeholders.
> > >
> > > 5) Website improvements
> > > The website keeps improving but this work is less dependent on the
> > > Camel 3.3 release.
> > >
> > > 6) Lightweight CamelContext
> > > gnodet will continue his experiment with this for really lightweight
> > > and fast Camel for graalvm/quarkus.
> > >
> > > 7) doInit vs doStart
> > > We should continue move and splitup initialization logic into early
> > > phase when possible.
> > >
> > > 8) Move reifiers to separate module / move model out of runtime
> > > If possible lets see if we can get more classes modularized so we can
> > > for example avoid having model classes at runtime if not needed.
> > >
> > > 9) Look at if we can align auto configuration of components in SB vs
> > camel-main
> > >
> > > And then the usual bunch of stuff with new components, bug fixes,
> > > dependency upgrades and whatnot.
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > > --
> > > Claus Ibsen
> > > -----------------
> > > http://davsclaus.com @davsclaus
> > > Camel in Action 2: https://www.manning.com/ibsen2
> >
> >
> >
> > --
> > Claus Ibsen
> > -----------------
> > http://davsclaus.com @davsclaus
> > Camel in Action 2: https://www.manning.com/ibsen2
> >
>
Re: [ROADMAP] - Apache Camel 3.3
Posted by Jean-Baptiste Onofre <jb...@nanthrax.net>.
Yeah, name is karaf-c for now, but it will probably change.
Regards
JB
> Le 4 mai 2020 à 10:13, Andrea Cosentino <an...@yahoo.com.INVALID> a écrit :
>
> About naming of feature, don't forget we already have a kamel executable in camel-k.. so if it's something different it would be better to use a different name
>
> Inviato da Yahoo Mail su Android
>
> Il lun, 4 mag, 2020 alle 9:58, Jean-Baptiste Onofre<jb...@nanthrax.net> ha scritto: Just to let you know that I gonna merge the camel-azure features in camel-karaf.
>
> I’m working on the new "kamel" feature (I will provide update on the mailing list soon).
>
> Regards
> JB
>
>
>> Le 4 mai 2020 à 09:52, Omar Al-Safi <om...@oalsafi.com> a écrit :
>>
>> +1
>>
>> On Thu, Apr 30, 2020 at 9:59 PM Gregor Zurowski <gr...@list.zurowski.org>
>> wrote:
>>
>>> +1
>>>
>>>
>>> On Thu, Apr 30, 2020, 5:19 PM Claus Ibsen <cl...@gmail.com> wrote:
>>>
>>>> Hi
>>>>
>>>> Just to get attention to this again. I would be good to finish up the
>>>> bits we can make and get Camel 3.3 timeboxed for release.
>>>>
>>>> So I suggest we by end of next week (friday) cut the RC. Then we can
>>>> get the release out here in start of May.
>>>> And then the 3.4 LTS release out in June / start of July (at latest).
>>>>
>>>> Any thoughts?
>>>>
>>>> On Wed, Apr 15, 2020 at 7:28 AM Claus Ibsen <cl...@gmail.com>
>>> wrote:
>>>>>
>>>>> Hi
>>>>>
>>>>> Lets keep the momentum going and release a new 3.x version next month.
>>>>> And lets aim for 3 weeks time. So if we can get Camel 3.3 released in
>>>>> start of / mid May 2020, then that would be great.
>>>>>
>>>>> Here are some of the areas to work on and see if we can get
>>>>> implemented and also the stuff already done.
>>>>>
>>>>> 1) Reflection free *DONE*
>>>>> We have continued the work to make Camel use less reflections and have
>>>>> now fixed the remainder bits in Rest DSL and Circuit Breakers.
>>>>> And there were some data formats that wasnt entirely fixed either.
>>>>>
>>>>> 2) Reflection free custom POJOs *DONE*
>>>>> We can now use @Configurer on custom POJOs and with our maven tool
>>>>> generate source code to configure without reflection
>>>>>
>>>>> 3) JAXB free *DONE*
>>>>> There were a few spots left to remove JAXB from the classpath when its
>>>>> not needed. Now Rest DSL is also free when you do not use XML
>>>>> bindings.
>>>>> And also remove JAXB from maven pom etc.
>>>>>
>>>>> 4) Bugs reported about Camel 3.2 *DONE*
>>>>> We have fixed the problems reported with Camel 3.2 such as install on
>>>>> karaf, or the endpoint-dsl not support property placeholders.
>>>>>
>>>>> 5) Website improvements
>>>>> The website keeps improving but this work is less dependent on the
>>>>> Camel 3.3 release.
>>>>>
>>>>> 6) Lightweight CamelContext
>>>>> gnodet will continue his experiment with this for really lightweight
>>>>> and fast Camel for graalvm/quarkus.
>>>>>
>>>>> 7) doInit vs doStart
>>>>> We should continue move and splitup initialization logic into early
>>>>> phase when possible.
>>>>>
>>>>> 8) Move reifiers to separate module / move model out of runtime
>>>>> If possible lets see if we can get more classes modularized so we can
>>>>> for example avoid having model classes at runtime if not needed.
>>>>>
>>>>> 9) Look at if we can align auto configuration of components in SB vs
>>>> camel-main
>>>>>
>>>>> And then the usual bunch of stuff with new components, bug fixes,
>>>>> dependency upgrades and whatnot.
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Claus Ibsen
>>>>> -----------------
>>>>> http://davsclaus.com @davsclaus
>>>>> Camel in Action 2: https://www.manning.com/ibsen2
>>>>
>>>>
>>>>
>>>> --
>>>> Claus Ibsen
>>>> -----------------
>>>> http://davsclaus.com @davsclaus
>>>> Camel in Action 2: https://www.manning.com/ibsen2
>>>>
>>>
>
R: Re: [ROADMAP] - Apache Camel 3.3
Posted by Andrea Cosentino <an...@yahoo.com.INVALID>.
About naming of feature, don't forget we already have a kamel executable in camel-k.. so if it's something different it would be better to use a different name
Inviato da Yahoo Mail su Android
Il lun, 4 mag, 2020 alle 9:58, Jean-Baptiste Onofre<jb...@nanthrax.net> ha scritto: Just to let you know that I gonna merge the camel-azure features in camel-karaf.
I’m working on the new "kamel" feature (I will provide update on the mailing list soon).
Regards
JB
> Le 4 mai 2020 à 09:52, Omar Al-Safi <om...@oalsafi.com> a écrit :
>
> +1
>
> On Thu, Apr 30, 2020 at 9:59 PM Gregor Zurowski <gr...@list.zurowski.org>
> wrote:
>
>> +1
>>
>>
>> On Thu, Apr 30, 2020, 5:19 PM Claus Ibsen <cl...@gmail.com> wrote:
>>
>>> Hi
>>>
>>> Just to get attention to this again. I would be good to finish up the
>>> bits we can make and get Camel 3.3 timeboxed for release.
>>>
>>> So I suggest we by end of next week (friday) cut the RC. Then we can
>>> get the release out here in start of May.
>>> And then the 3.4 LTS release out in June / start of July (at latest).
>>>
>>> Any thoughts?
>>>
>>> On Wed, Apr 15, 2020 at 7:28 AM Claus Ibsen <cl...@gmail.com>
>> wrote:
>>>>
>>>> Hi
>>>>
>>>> Lets keep the momentum going and release a new 3.x version next month.
>>>> And lets aim for 3 weeks time. So if we can get Camel 3.3 released in
>>>> start of / mid May 2020, then that would be great.
>>>>
>>>> Here are some of the areas to work on and see if we can get
>>>> implemented and also the stuff already done.
>>>>
>>>> 1) Reflection free *DONE*
>>>> We have continued the work to make Camel use less reflections and have
>>>> now fixed the remainder bits in Rest DSL and Circuit Breakers.
>>>> And there were some data formats that wasnt entirely fixed either.
>>>>
>>>> 2) Reflection free custom POJOs *DONE*
>>>> We can now use @Configurer on custom POJOs and with our maven tool
>>>> generate source code to configure without reflection
>>>>
>>>> 3) JAXB free *DONE*
>>>> There were a few spots left to remove JAXB from the classpath when its
>>>> not needed. Now Rest DSL is also free when you do not use XML
>>>> bindings.
>>>> And also remove JAXB from maven pom etc.
>>>>
>>>> 4) Bugs reported about Camel 3.2 *DONE*
>>>> We have fixed the problems reported with Camel 3.2 such as install on
>>>> karaf, or the endpoint-dsl not support property placeholders.
>>>>
>>>> 5) Website improvements
>>>> The website keeps improving but this work is less dependent on the
>>>> Camel 3.3 release.
>>>>
>>>> 6) Lightweight CamelContext
>>>> gnodet will continue his experiment with this for really lightweight
>>>> and fast Camel for graalvm/quarkus.
>>>>
>>>> 7) doInit vs doStart
>>>> We should continue move and splitup initialization logic into early
>>>> phase when possible.
>>>>
>>>> 8) Move reifiers to separate module / move model out of runtime
>>>> If possible lets see if we can get more classes modularized so we can
>>>> for example avoid having model classes at runtime if not needed.
>>>>
>>>> 9) Look at if we can align auto configuration of components in SB vs
>>> camel-main
>>>>
>>>> And then the usual bunch of stuff with new components, bug fixes,
>>>> dependency upgrades and whatnot.
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Claus Ibsen
>>>> -----------------
>>>> http://davsclaus.com @davsclaus
>>>> Camel in Action 2: https://www.manning.com/ibsen2
>>>
>>>
>>>
>>> --
>>> Claus Ibsen
>>> -----------------
>>> http://davsclaus.com @davsclaus
>>> Camel in Action 2: https://www.manning.com/ibsen2
>>>
>>
Re: [ROADMAP] - Apache Camel 3.3
Posted by Jean-Baptiste Onofre <jb...@nanthrax.net>.
Just to let you know that I gonna merge the camel-azure features in camel-karaf.
I’m working on the new "kamel" feature (I will provide update on the mailing list soon).
Regards
JB
> Le 4 mai 2020 à 09:52, Omar Al-Safi <om...@oalsafi.com> a écrit :
>
> +1
>
> On Thu, Apr 30, 2020 at 9:59 PM Gregor Zurowski <gr...@list.zurowski.org>
> wrote:
>
>> +1
>>
>>
>> On Thu, Apr 30, 2020, 5:19 PM Claus Ibsen <cl...@gmail.com> wrote:
>>
>>> Hi
>>>
>>> Just to get attention to this again. I would be good to finish up the
>>> bits we can make and get Camel 3.3 timeboxed for release.
>>>
>>> So I suggest we by end of next week (friday) cut the RC. Then we can
>>> get the release out here in start of May.
>>> And then the 3.4 LTS release out in June / start of July (at latest).
>>>
>>> Any thoughts?
>>>
>>> On Wed, Apr 15, 2020 at 7:28 AM Claus Ibsen <cl...@gmail.com>
>> wrote:
>>>>
>>>> Hi
>>>>
>>>> Lets keep the momentum going and release a new 3.x version next month.
>>>> And lets aim for 3 weeks time. So if we can get Camel 3.3 released in
>>>> start of / mid May 2020, then that would be great.
>>>>
>>>> Here are some of the areas to work on and see if we can get
>>>> implemented and also the stuff already done.
>>>>
>>>> 1) Reflection free *DONE*
>>>> We have continued the work to make Camel use less reflections and have
>>>> now fixed the remainder bits in Rest DSL and Circuit Breakers.
>>>> And there were some data formats that wasnt entirely fixed either.
>>>>
>>>> 2) Reflection free custom POJOs *DONE*
>>>> We can now use @Configurer on custom POJOs and with our maven tool
>>>> generate source code to configure without reflection
>>>>
>>>> 3) JAXB free *DONE*
>>>> There were a few spots left to remove JAXB from the classpath when its
>>>> not needed. Now Rest DSL is also free when you do not use XML
>>>> bindings.
>>>> And also remove JAXB from maven pom etc.
>>>>
>>>> 4) Bugs reported about Camel 3.2 *DONE*
>>>> We have fixed the problems reported with Camel 3.2 such as install on
>>>> karaf, or the endpoint-dsl not support property placeholders.
>>>>
>>>> 5) Website improvements
>>>> The website keeps improving but this work is less dependent on the
>>>> Camel 3.3 release.
>>>>
>>>> 6) Lightweight CamelContext
>>>> gnodet will continue his experiment with this for really lightweight
>>>> and fast Camel for graalvm/quarkus.
>>>>
>>>> 7) doInit vs doStart
>>>> We should continue move and splitup initialization logic into early
>>>> phase when possible.
>>>>
>>>> 8) Move reifiers to separate module / move model out of runtime
>>>> If possible lets see if we can get more classes modularized so we can
>>>> for example avoid having model classes at runtime if not needed.
>>>>
>>>> 9) Look at if we can align auto configuration of components in SB vs
>>> camel-main
>>>>
>>>> And then the usual bunch of stuff with new components, bug fixes,
>>>> dependency upgrades and whatnot.
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Claus Ibsen
>>>> -----------------
>>>> http://davsclaus.com @davsclaus
>>>> Camel in Action 2: https://www.manning.com/ibsen2
>>>
>>>
>>>
>>> --
>>> Claus Ibsen
>>> -----------------
>>> http://davsclaus.com @davsclaus
>>> Camel in Action 2: https://www.manning.com/ibsen2
>>>
>>