You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by Antoine DESSAIGNE <an...@gmail.com> on 2022/09/05 08:25:34 UTC
Jakarta migration
Hello everyone,
I just noticed that the Jira tickets related to the Jakarta migration now
have the 4.0 expected fix version. I couldn't find any blog post or
conversation regarding when this 4.0 could be released. I'm not asking for
a definitive date but rather a quarter/semester of when you hope that will
happen.
Also, I'm a bit worried to include this dependency change with other major
changes like the change of URI. Wouldn't it be better to follow the Jetty
approach and have a 4.x identical to 3.x but using the Jakarta namespace
instead of the Javax namespace and then a 5.x branch for new developments?
Thank you very much for your feedback.
Have a nice day,
Antoine.
Re: Jakarta migration
Posted by Claus Ibsen <cl...@gmail.com>.
Hi
Yeah Camel v4 is more of a "soft" upgrade with primary focus on the javax
-> jakarta migration, which frankly affects a lot.
Camel has many components that are using JEE spec JARs and they are all
needed to be upgraded / migrated.
The Quarkus team has been working on this as they are even more affected.
And they react to various projects for them to release jakarta releases etc.
The URI thing is an internal complexity because we have used java.net.URI
to parse since Camel was created, but we don't do that as much anymore.
From the end user point of view the goal is that they are not affected.
On Mon, Sep 5, 2022 at 10:44 AM Antoine DESSAIGNE <
antoine.dessaigne@gmail.com> wrote:
> Hi Claus,
>
> Thank you for the quick reply and I agree with you I wouldn't do anything
> in Camel v3
>
> In fact, because it's a big change and has a big impact I wouldn't include
> any other big changes with it (like URI handling). In any case, I'll look
> forward to the discussion around Camel 4.0.
>
> Antoine
>
> Le lun. 5 sept. 2022 à 10:32, Claus Ibsen <cl...@gmail.com> a écrit
> :
>
> > Hi
> >
> > Camel 4 discussions will open up this fall.
> > At first we are working on new releases 3.18.2 and 3.19.0.
> >
> > The jakarta changes are big and impacts also the spring framework /
> spring
> > boot / quarkus,
> > where they are working on this too, so at first sight its a big major
> > release - spring 6, boot 3, quarkus 3 et all.
> >
> > No we will not do any changes in Camel v3 - this will be as-is.
> >
> >
> >
> > On Mon, Sep 5, 2022 at 10:25 AM Antoine DESSAIGNE <
> > antoine.dessaigne@gmail.com> wrote:
> >
> > > Hello everyone,
> > >
> > > I just noticed that the Jira tickets related to the Jakarta migration
> now
> > > have the 4.0 expected fix version. I couldn't find any blog post or
> > > conversation regarding when this 4.0 could be released. I'm not asking
> > for
> > > a definitive date but rather a quarter/semester of when you hope that
> > will
> > > happen.
> > >
> > > Also, I'm a bit worried to include this dependency change with other
> > major
> > > changes like the change of URI. Wouldn't it be better to follow the
> Jetty
> > > approach and have a 4.x identical to 3.x but using the Jakarta
> namespace
> > > instead of the Javax namespace and then a 5.x branch for new
> > developments?
> > >
> > > Thank you very much for your feedback.
> > >
> > > Have a nice day,
> > >
> > > Antoine.
> > >
> >
> >
> > --
> > 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: Jakarta migration
Posted by Antoine DESSAIGNE <an...@gmail.com>.
Hi Claus,
Thank you for the quick reply and I agree with you I wouldn't do anything
in Camel v3
In fact, because it's a big change and has a big impact I wouldn't include
any other big changes with it (like URI handling). In any case, I'll look
forward to the discussion around Camel 4.0.
Antoine
Le lun. 5 sept. 2022 à 10:32, Claus Ibsen <cl...@gmail.com> a écrit :
> Hi
>
> Camel 4 discussions will open up this fall.
> At first we are working on new releases 3.18.2 and 3.19.0.
>
> The jakarta changes are big and impacts also the spring framework / spring
> boot / quarkus,
> where they are working on this too, so at first sight its a big major
> release - spring 6, boot 3, quarkus 3 et all.
>
> No we will not do any changes in Camel v3 - this will be as-is.
>
>
>
> On Mon, Sep 5, 2022 at 10:25 AM Antoine DESSAIGNE <
> antoine.dessaigne@gmail.com> wrote:
>
> > Hello everyone,
> >
> > I just noticed that the Jira tickets related to the Jakarta migration now
> > have the 4.0 expected fix version. I couldn't find any blog post or
> > conversation regarding when this 4.0 could be released. I'm not asking
> for
> > a definitive date but rather a quarter/semester of when you hope that
> will
> > happen.
> >
> > Also, I'm a bit worried to include this dependency change with other
> major
> > changes like the change of URI. Wouldn't it be better to follow the Jetty
> > approach and have a 4.x identical to 3.x but using the Jakarta namespace
> > instead of the Javax namespace and then a 5.x branch for new
> developments?
> >
> > Thank you very much for your feedback.
> >
> > Have a nice day,
> >
> > Antoine.
> >
>
>
> --
> Claus Ibsen
> -----------------
> http://davsclaus.com @davsclaus
> Camel in Action 2: https://www.manning.com/ibsen2
>
Re: Jakarta migration
Posted by Claus Ibsen <cl...@gmail.com>.
Hi
Camel 4 discussions will open up this fall.
At first we are working on new releases 3.18.2 and 3.19.0.
The jakarta changes are big and impacts also the spring framework / spring
boot / quarkus,
where they are working on this too, so at first sight its a big major
release - spring 6, boot 3, quarkus 3 et all.
No we will not do any changes in Camel v3 - this will be as-is.
On Mon, Sep 5, 2022 at 10:25 AM Antoine DESSAIGNE <
antoine.dessaigne@gmail.com> wrote:
> Hello everyone,
>
> I just noticed that the Jira tickets related to the Jakarta migration now
> have the 4.0 expected fix version. I couldn't find any blog post or
> conversation regarding when this 4.0 could be released. I'm not asking for
> a definitive date but rather a quarter/semester of when you hope that will
> happen.
>
> Also, I'm a bit worried to include this dependency change with other major
> changes like the change of URI. Wouldn't it be better to follow the Jetty
> approach and have a 4.x identical to 3.x but using the Jakarta namespace
> instead of the Javax namespace and then a 5.x branch for new developments?
>
> Thank you very much for your feedback.
>
> Have a nice day,
>
> Antoine.
>
--
Claus Ibsen
-----------------
http://davsclaus.com @davsclaus
Camel in Action 2: https://www.manning.com/ibsen2