Hello Richard,
Just in case my position on this question was not clear:
HUGE +1 for Java 17 base line, to get both AMQ6 & CXF 4.1 in a near future.
(non binding, sorry)
Alex
Le ven. 5 avr. 2024 à 16:01, Richard Zowalla a écrit :
>
> Hi JB,
>
> thanks for the info. Guess we will come back to
Hi JB,
thanks for the info. Guess we will come back to your offer once there
is a decission regarding the java baseline.
Just started a discussion if we can move "main" (TomEE 10) to a Java 17
baseline in order to integrate AMQ6 + CXF 4.1 in the near future.
Gruß
Richard
Am Donnerstag, dem
Hi Richard,
Just a minor note about ActiveMQ 6.x: the JMS3 support is not yet
full, meaning that some specific operations can throw
OperationNotSupportedException.
ActiveMQ 6.1.1 is currently on vote (I will release it tomorrow),
including a couple of new JMS3 operations.
I estimate that JMS3
JakartaEE 11 has 17 as a baseline for EE10 it is only 11.
Ursprüngliche Nachricht Von: Alex The Rocker
Datum: 31.03.24 13:22 (GMT+01:00) An:
dev@tomee.apache.org Betreff: Re: AMQ6 in TomEE 10 Huge +1 for AMQ6.Requiring
Java 17+ isn't a problem, since (unless I'm mistaken
JakartaEE 11 has 17 as a baseline for EE10 it is only 11.
Ursprüngliche Nachricht Von: Alex The Rocker
Datum: 31.03.24 13:22 (GMT+01:00) An:
dev@tomee.apache.org Betreff: Re: AMQ6 in TomEE 10 Huge +1 for AMQ6.Requiring
Java 17+ isn't a problem, since (unless I'm mistaken
From EE10 spec perspective, it requires 11+ , see
https://jakarta.ee/specifications/platform/10/
Am 31. März 2024 13:21:56 MESZ schrieb Alex The Rocker :
>Huge +1 for AMQ6.
>
>Requiring Java 17+ isn't a problem, since (unless I'm mistaken)
>Jakarta EE 10 requires Java 17.
>
>Thanks,
>Alex
>
>
Huge +1 for AMQ6.
Requiring Java 17+ isn't a problem, since (unless I'm mistaken)
Jakarta EE 10 requires Java 17.
Thanks,
Alex
Le dim. 31 mars 2024 à 11:59, Thomas Andraschko
a écrit :
>
> If we are allowed to set baseline to +17, im ok with it.
> New user can just use 17 and existing users
If we are allowed to set baseline to +17, im ok with it.
New user can just use 17 and existing users can easily upgrade Java when
they already migrate their whole code to Jakarta.
Richard Zowalla schrieb am So., 31. März 2024, 11:31:
> Hi all,
>
> just looked into AMQ (classic) 6.1.0 (JMS 3.1),
Hi all,
just looked into AMQ (classic) 6.1.0 (JMS 3.1), which seems to be fully
Jakarta compatible (currently running a CI build on a related branch).
However, it requires Java 17 as a baseline (meh).
Since EE10 targets Java 11+ (and not 17+), the question would be, if we
can/want to upgrade?
