Hi all,

Sounds very good overall but would be great to not do it at the cost to
break tomcat IDE support maybe - current status since it uses a single
module and not all IDE support to compile supackages with different target
versions?
Overall stays an Apache project where we should ensure we make
contributions easy ;).

Indeed just my 2cts feedback.

Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> |  Blog
<https://rmannibucau.metawerx.net/> | Old Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
LinkedIn <https://www.linkedin.com/in/rmannibucau> | Book
<https://www.packtpub.com/application-development/java-ee-8-high-performance>


Le ven. 23 févr. 2024 à 16:08, Mark Thomas <ma...@apache.org> a écrit :

> On 23/02/2024 13:35, Rémy Maucherat wrote:
> > Hi,
> >
> > I would like to propose backporting the OpenSSL FFM support to Tomcat
> 10.1.
> >
> > Java 22.0.0 should be released on March 19, and the next Java LTS
> > should still have no problem targeting Java 11. As a result, there
> > should be no negative impact to the platform support, and users
> > running on Java 22+ could benefit from easier OpenSSL support.
> >
> > Obviously I anticipate most users will use FFM support once the next
> > Java LTS is out in a few years, but getting the feature out now would
> > still be good.
> >
> > After the change:
> > - Compiling, running the testsuite, etc is still doable with Java 17.
> > - Running Tomcat 10.1 still works with Java 11.
> > - Building a Tomcat 10.1 release would now require Java 22+.
> >
> > Backporting further to Tomcat 9.0 could be riskier however. Following
> > the removal of the Java 7 release target, Java 8 might be next. The
> > main question is if the next Java LTS will still support the Java 8
> > release target.
> >
> > Comments ?
>
> LGTM.
>
> Mark
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: dev-h...@tomcat.apache.org
>
>

Reply via email to