Hey Richard, huge +1 from my side to start work on EE 11, our goal really shouldn't be to lag behind one EE version. There are of course external factors we can’t control but as soon as it’s reasonably possible we should start working towards EE 11.
Just listing some potential roadblockers i can think of right now to get those on the list and not just in private conversations (probably far from complete): - we need a CXF 4.2 release, potentially someone could run a release interim like we did with EE 10 when https://github.com/apache/cxf/pull/2473 is merged - what do we do about JPA? stick to OpenJPA and worry about Jakarta Data, or switch to Hibernate 7 which is now Apache licensed and also comes with Jakarta Data - Some dependencies haven’t begun working on upgrades yet, e.g. OWB is still on CDI 4.0 - Impls for specifications that are built in will need a good amount of work (I know both security and concurrency need will need some attention as I worked on that code before) I agree with you that it would make the most sense to update our API shade and based on the changes needed there we look into the individual specs. IMO it makes sense to list in a ticket what 1. is ready and we just need to update dependencies (e.g. MyFaces) 2. dependencies we need to wait for/help (e.g. OWB) 3. work that needs to be done in TomEE directly (e.g. Concurrency) Thanks Markus > On 16. Sep 2025, at 13:46, Richard Zowalla <r...@apache.org> wrote: > > Hi all, > > I’d like to propose that we start work on a Jakarta EE 11 API shade in > https://github.com/apache/tomee-jakartaee-api (create a ee10 branch, move > main to e11 and do a first milestone release) > > This would give us a solid baseline to begin the upgrade path from TomEE > 10.1.x to TomEE 11. > > In addition, we should create a ticket that documents all the specification > differences between Jakarta EE 10 and 11. That way we can clearly see what > changes are required and identify where updates or enhancements are needed in > the TomEE codebase. > > This is not about TCKs at this stage (since that remains a larger challenge > we couldn’t fully tackle with TomEE 10), but rather about getting a clear > picture of the work ahead and aligning on the upgrade path. > > WDYT? > > Richard
