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 <claus.ib...@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.dessai...@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
>

Reply via email to