[wildfly-dev] Re: Shared topic branch for Jakarta EE 11

What is our Jakarta Concurrency implementation? On Fri, Jan 26, 2024 at 1:56 PM Brian Stansberry <brian.stansberry(a)redhat.com&gt; wrote: > > I have pushed a new 'EE11' branch to wildfly/wildfly. This can serve as a shared topic branch as we explore Jakarta EE 11 support for WildFly. > > I think anything we do with this branch at this point should be restricted to WildFly Preview. Hopefully initial work can be limited to using different component versions as EE 11 artifacts become available. There will be breaking changes in EE 11 vs 10, but hopefully little or none that affects our integration code. At this stage these do not need to be Final/GA artifacts. > > At this point the only difference between the EE11 and main branches is one commit to require use of SE 17+ to build, while still requiring SE 11 as the source/target/release version. We'll need to compile against SE 17 dependencies, but at this point there's not a strong need for our own code to move beyond SE 11, and staying there gives us the greatest flexibility. For more see https://issues.redhat.com/browse/WFLY-18967. > > Best regards, > > -- > Brian Stansberry > Principal Architect, Red Hat JBoss EAP > WildFly Project Lead > He/Him/His > _______________________________________________ > wildfly-dev mailing list -- wildfly-dev(a)lists.jboss.org > To unsubscribe send an email to wildfly-dev-leave(a)lists.jboss.org > Privacy Statement: https://www.redhat.com/en/about/privacy-policy > List Archives: https://lists.jboss.org/archives/list/wildfly-dev@lists.jboss.org/message...