JakartaEE 11 has 17 as a baseline for EE10 it is only 11.
-------- Ursprüngliche Nachricht --------Von: Alex The Rocker
<alex.m3...@gmail.com> 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)Jakarta EE 10 requires
Java 17.Thanks,AlexLe dim. 31 mars 2024 à 11:59, Thomas
Andraschko<andraschko.tho...@gmail.com> a écrit :>> 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 <r...@apache.org> schrieb am So., 31. März 2024,
11:31:>> > 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? From a spec perspective, I assume, that we cannot.> >> >
Why AMQ6: It would enable us to drop some of our shaded dependencies> > (and
would be a thing for EE11 anyway).> >> > I am not familiar with the TCK
requirements or if it is possible to> > only support one JVM runtime for
certification? At a first glance at> > [1], there are vendors (fujitsu), who
only did the TCK runs on Java 17,> > but I am not familiar with the actual
details of the process.> >> > Happy to get some thoughts on it.> >> > (Not
planning to have such a change in the proposed milestone, just> > want to get
some thoughts on it)> >> > Gruß> > Richard> >> >> > [1]
https://jakarta.ee/compatibility/certification/10/> >