On Tue, Feb 20, 2024 at 5:08 PM Mark Thomas <ma...@apache.org> wrote: > > Looking at the latest version of the Jakarta EE 11 release plan, the > minimum Java version has been dropped to Java 17. > > https://jakartaee.github.io/platform/jakartaee11/JakartaEE11ReleasePlan > > On that basis I think we have no choice but to reduce the minimum Java > version for Tomcat 11 to Java 17. > > I have a branch with this change already in place. If there are no > objections I'll merge those changes later this week.
+1 if you have already done it. (otherwise I could work on it) Rémy > Mark > > > On 19/01/2024 16:45, Volodymyr Siedlecki wrote: > > Hi, > > > > This is more compliance than function, unfortunately. Open Liberty > > plans to pass the TCK under both 17 and 21 (although only one is > > required). > > > > If the EL jar we use is Java 21 byte code, then we wouldn't be able to > > run the Jakarta EE 11 features on 17. > > > > If Tomcat could compile EL against 17, that would be a huge help. If > > not, we have workarounds. > > > > Volodymyr > > > > > > On Fri, Jan 19, 2024 at 9:41 AM Mark Thomas <ma...@apache.org> wrote: > > > >> On 19/01/2024 14:20, Volodymyr Siedlecki wrote: > >>> Hi Mark, > >>> > >>> I understand your perspective about changing 21 to 17 so late. > >>> > >>> Open Liberty uses Tomcat's Expression Language and we would prefer to > >>> use a Java 17 binary. However, there are workarounds for us. > >> > >> Ack. > >> > >> I'll note that the EL code will compile quite happily with Java 17 or > >> Java 21. > >> > >> Can you expand on why you'd prefer Java 17? Ignoring how late in the > >> process this change is being made, I've yet to hear a logically > >> consistent argument for selecting Java 17 over Java 21. > >> > >>> As for the EL TCK issue, I'd be happy to take a look if you push up a > >> branch. > >> > >> Thanks for the offer but I have already fixed the issue. > >> > >> Mark > >> > >> > >>> > >>> Thank you, > >>> > >>> Volodymyr > >>> > >>> > >>> On Fri, Jan 19, 2024 at 6:38 AM Mark Thomas <ma...@apache.org> wrote: > >>> > >>>> On 16/01/2024 11:44, Rémy Maucherat wrote: > >>>>> On Tue, Jan 16, 2024 at 11:59 AM Mark Thomas <ma...@apache.org> wrote: > >>>>>> > >>>>>> Hi all, > >>>>>> > >>>>>> I'm not sure what is going on as there has been one significant change > >>>>>> in the announcement already but it looks to me as if the minimum Java > >>>>>> version for Jakarta EE 11 is changing to Java 17 rather than Java 21. > >>>>>> > >>>>>> https://www.eclipse.org/lists/jakartaee-platform-dev/msg04371.html > >>>>>> > >>>>>> It seems far too late in the day for this change to me but I'm not > >> sure > >>>>>> that view is going to carry much weight. > >>>>>> > >>>>>> I've taken a quick look at the Tomcat 11 code base and a JreCompat for > >>>>>> Java 21 shouldn't be too much work. I'm not planning on doing anything > >>>>>> on this until the intentions of the Jakarta EE platform team are > >>>> clearer. > >>>>> > >>>>> That's annoying ... The virtual threads are in the 21 compat. The > >>>>> Panama for Java 22 and building releases with 22+ should not require > >>>>> any additional changes. > >>>> > >>>> I'm going to be looking at switching Java 17 locally as I have an EL TCK > >>>> issue I need to investigate that only happens on Java 17. I can push > >>>> that branch to GitHub if there is interest. However, I am a long way > >>>> from being ready to support that change for 11.0.x. > >>>> > >>>> I ma trying to think about this in terms of what would be best for our > >>>> user community. > >>>> > >>>> Working to a minimum of Java 17 would make Tomcat 11 an option for those > >>>> using willing to move to Java 17 but unwilling to move to Java 21. What > >>>> I am not sure about is how big a proportion of our community that is. If > >>>> I had to guess, I'd say very small. > >>>> > >>>> Working to a minimum of Java 21 would mean users could be sure that > >>>> anything claiming Jakarta 11 compliance would work with Tomcat - whether > >>>> it required Java 17 or Java 21 as a minimum. > >>>> > >>>> Given the above, I'm leaning towards sticking with Java 21 as the > >>>> minimum unless there is user demand for Java 17. I'll note that we can > >>>> always reduce the minimum version at any point in the future - even > >>>> between stable point releases. > >>>> > >>>> Mark > >>>> > >>>> --------------------------------------------------------------------- > >>>> To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org > >>>> For additional commands, e-mail: dev-h...@tomcat.apache.org > >>>> > >>>> > >>> > >> > >> --------------------------------------------------------------------- > >> To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org > >> For additional commands, e-mail: dev-h...@tomcat.apache.org > >> > >> > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org > For additional commands, e-mail: dev-h...@tomcat.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
