Hi all, I have just updated our CI build definitions, created tomee-10.x and merged ee11 into main, so the current development is reflected on the main part of the GitHub repo ;-)
Gruß Richard > Am 18.11.2025 um 13:37 schrieb Markus Jung <[email protected]>: > > Hey David, > > > I'm +1 for merging EE11 into the main branch. IMO a main branch is where the > main development happens and not some sort of stable branch, with the actual > work happening being hidden away in a separate branch. In its current state > it will obviously break the build. For me that's okay since TomEE 11 is still > in its _very_ early stages. IMO fixing these tests should also be a higher > priority than working on e.g. our security/concurrency implementations. > > > Thanks > Markus > > On 11/18/25 01:37, David Blevins wrote: >> Thanks for this update, Richard. Thanks also Markus for the work. >> >> What does everyone think about making this branch the main branch? >> >> People looking for stable branches can easily find them. People looking to >> see activity in main can easily miss the branch. >> >> >> -David >> >> >>> On Nov 16, 2025, at 12:18 AM, Richard Zowalla <[email protected]> wrote: >>> >>> Hi all, >>> >>> Markus and myself started the work on EE11 on this branch: [1] >>> >>> What is currently done: >>> >>> 1.) Markus upgraded the EE API Shade to EE11. Notably, some APIs were >>> dropped that we still need in TomEE, so work was done to add those APIs >>> back into TomEE (JAXB, etc.). >>> 2. ) We are currently using a custom CXF fork based on Reta’s work on >>> CXF-8828 [2]. Similar to EE10, I forked his work branch and created an >>> intermediate custom release until CXF provides something official. The >>> forked code is available here: [3]. >>> 3.) Although EE11 targets Java 17/21, the CXF team would like to require >>> Java 21. I’ve commented on that, but it would be great if others could also >>> voice their preference for Java 17 over Java 21 as the baseline. >>> An alternative would be to adopt Java 21 as the baseline for TomEE 11: [4]. >>> Currently, the baseline on the ee11 branch is set to Java 21 (as the >>> intermediate CXF fork did require it). >>> 4.) Build looks good so far. The tests, which are failing right now, are >>> all related to the removal of the SecurityManager in Java 21. The build is >>> here: [5] >>> >>> On our upstream dependencies: >>> >>> - Work has started on OpenJPA for JPA 3.2 on a separate branch / repo, so >>> not out to see in the original repo. I think, that help would be welcome on >>> their side. >>> - CXF has also started working on EE11 (see above) >>> - OWB also started for the CDI part. >>> - MyFaces is already EE 11 ready (afaik) >>> >>> What needs to be done: >>> >>> - Next step on our side would be to start implementing the changes for the >>> specs (security, concurrency, …) which are implemented in TomEE itself. >>> - We need to discuss how we want to deal with Jakarta Data (new spec); >>> would need to be implemented either as a separate project or in TomEE >>> itself. >>> - Look into MicroProfile 7+ upgrades ;-) >>> >>> More updates will follow as the work progresses. >>> Feedback, testing, and comments are very welcome. >>> >>> Gruß >>> Richard >>> >>> [1] https://github.com/apache/tomee/tree/ee11 >>> [2] https://github.com/reta/cxf/tree/CXF-8828 >>> [3] https://github.com/rzo1/cxf/tree/CXF-8828 >>> [4] https://issues.apache.org/jira/browse/CXF-8828 >>> [5] https://ci-builds.apache.org/job/Tomee/job/tomee11-full/ >>>
