The people this change might impact is anyone using Arq to test their apps against WildFly Preview 26.x (or earlier) on SE 8. But I think anyone doing that can stick to WF Arq 5.0.0.Alpha5 (or any later release you make before making this SE baseline change.) WFP 26.x itself was tested using WF Arq 5.0.0.Alpha#.

On Wed, Nov 2, 2022 at 5:48 PM James Perkins <jperkins(a)redhat.com&gt; wrote: > Hello All, > WildFly Arquillian has 2 community supported versions right now, 5 and 4. > Currently 5 targets Jakarta EE 9 and Java 8. The only compliant Jakarta EE > 9/9.1 WildFly containers are WildFly Preview 22+. > > WildFly 27 will be the next community supported which targets Jakarta EE > 10 and therefore Java 11. I would like to migrate WildFly Arquillian to > require a minimum runtime of Java 11. However, we could keep the Jakarta EE > 9 support as we don't use anything specific to Jakarta EE 10 currently. > > Why do this? If we can require Java 11 we can upgrade WildFly Core to > 19.x. This gives users of WildFly 27 better support for booting WildFly 27 > with the appropriate JVM arguments. It also allows us to align better with > WildFly 27+ in the future. > > My question is, does anyone oppose making Java 11 the minimum runtime for > WildFly Arquillian 5? We will continue to target Jakarta EE 9 components, > e.g. jakarta.servlet:jakarta.servlet-api:5.0. We will also leave WildFly > Arquillian 4 targeting Jakarta EE 8 and Java 8. > > -- > James R. Perkins > JBoss by Red Hat > _______________________________________________ > wildfly-dev mailing list -- wildfly-dev(a)lists.jboss.org > To unsubscribe send an email to wildfly-dev-leave(a)lists.jboss.org > %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s -- Brian Stansberry Principal Architect, Red Hat JBoss EAP He/Him/His