Sure, issue is created:
https://issues.apache.org/jira/browse/CAMEL-20080
Raymond
On Sat, Nov 4, 2023 at 10:17 AM Andrea Cosentino wrote:
> Il ven 3 nov 2023, 09:33 ski n ha scritto:
>
> > Sorry, I forgot to mention. This was tested with Camel 3.20.7 (JDK 11).
> >
> > btw: I'm also in the pr
Il ven 3 nov 2023, 09:33 ski n ha scritto:
> Sorry, I forgot to mention. This was tested with Camel 3.20.7 (JDK 11).
>
> btw: I'm also in the progress to upgrade to 4, but that has some caveats.
> This is not because of Camel, but more of other things like Junit5,
> Jakarta, ActiveMQ, Java17+.et
OK, thanks for the notice. I can test a patch for example for 3.20.9 when
needed.
On Sat, Nov 4, 2023 at 10:07 AM Otavio Rodolfo Piske
wrote:
> Hi,
>
> I think this might be this issue or related to it:
> https://issues.apache.org/jira/browse/CAMEL-19849.
>
> It needs to be investigated further
Hi,
I think this might be this issue or related to it:
https://issues.apache.org/jira/browse/CAMEL-19849.
It needs to be investigated further.
Kind regards
On Fri, Nov 3, 2023 at 9:33 AM ski n wrote:
> Sorry, I forgot to mention. This was tested with Camel 3.20.7 (JDK 11).
>
> btw: I'm al