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