I wouldn't call it "certified" ;) Am Mittwoch, dem 15.09.2021 um 08:33 +0000 schrieb COURTAULT Francois: > Hello, > > So TomEE 8.0.8 is certified on JDK 16 but not yet on JDK 17: is this > correct ? > > Best Regards. > > -----Original Message----- > From: Zowalla, Richard <[email protected]> > Sent: mercredi 15 septembre 2021 09:49 > To: [email protected] > Subject: Re: Is the new TomEE version 8.0.8 certified on JDK 17 ? > > No. It was discussed on the vote for 8.0.8 but should be a subject > for > 8.0.9 imho. > > We have a production system (simple JSF webapp + JAX-RS - nothing > complicated) running with J16 for a few weeks now (before 8.0.8 - it > was a custom 8.0.8-SNAPSHOT build...). It was required to add -- > illegal-access=permit to the configuration but worked fine. Did not > do > any tests with 17, yet. > > Gruss > Richard > > Am Mittwoch, dem 15.09.2021 um 08:50 +0200 schrieb Alex The Rocker: > > Good question! > > > > I have myself ran some tests with JDK 16, found a few glitches > > (already tracked by some JIRAs), but no blockers. > > > > I haven't yet started with JDK17 (waiting for my favorite OpenJ9- > > based > > Java version to deliver JDK17 level, which soon take place soon). > > > > Anyway the question of certifying TomEE with this new LTS (Long > > Term > > Support) version of Java must be raised - I don't see how it could > > not > > be the case. > > > > Alex > > > > Le mer. 15 sept. 2021 à 08:35, COURTAULT Francois > > <[email protected]> a écrit : > > > Hello, > > > > > > The question I want to ask is in the email Subject. > > > > > > Best Regards. > > > > > > > > >
smime.p7s
Description: S/MIME cryptographic signature
