Hi all, well done, Mark. I would go with 17 at this point, too.
Cheers, Arne OPEN KNOWLEDGE GmbH Poststraße 1, 26122 Oldenburg Mobil: +49 151 - 108 22 942 Tel: +49 441 - 4082-154 Fax: +49 441 - 4082-111 arne.limb...@openknowledge.de<mailto:arne.limb...@openknowledge.de> http://www.openknowledge.de/<https://www.openknowledge.de/> Registergericht: Amtsgericht Oldenburg, HRB 4670 Geschäftsführer: Lars Röwekamp, Jens Schumann Treffen Sie uns auf kommenden Konferenzen und Workshops: Zu unseren Events<https://www.openknowledge.de/event/> Von: Romain Manni-Bucau <rmannibu...@gmail.com> Datum: Dienstag, 4. Juni 2024 um 13:38 An: dev@openwebbeans.apache.org <dev@openwebbeans.apache.org> Betreff: Re: Meecrowave-2.0.x Hi, I don't care much but think java 21 will not bring anything to the codebase so 17 sounds as the best compromise from my window. Romain Manni-Bucau @rmannibucau Le mar. 4 juin 2024 à 12:58, Richard Zowalla <rich...@zowalla.com> a écrit : > Hi, > > personally, I would favor 17 as a baseline for now. > Might be less confusing for people in the EE-verse as it it would be > roughly aligned with the EE spec java version. > > Gruß > r > > > Am 04.06.2024 um 12:33 schrieb Mark Struberg <strub...@yahoo.de.INVALID > >: > > > > hi! > > > > I did start to work on moving Meecrowave to natively support jakartaEE > without shading right now while at ApacheConEU. > > > > Which target JVM should we target? Is 21 fine? Is there any need to > still support Java17? > > > > LieGrue, > > strub > >
