Good discussion with great questions. A couple updates/points: - Jakarta EE 9 has entirely removed requirements and tests for CORBA/ORB support (resolved and executed)
- Java 11 may or may not stay as the target jvm version for Jakarta EE 9 (new discussion https://www.eclipse.org/lists/jakartaee-spec-project-leads/msg00600.html) - TomEE 8x being the master branch, we have some stability limitations on removing/adding major features Here's where I think that pushes us. CORBA/ORB We probably don't want to be adding CORBA support. We maybe could have gotten some small benefit 10 years ago when it would have allowed us to pursue Java EE Full Profile certification, but with it being dropped by the JDK and Jakarta platform we'd be setting ourselves up to have to carry a ton of weight. That brings us remove vs maintain, which really becomes a stability question linked to the fact that TomEE 8.0.x is living in master. We might want to explore ways to support the very limited ties we have without a compile time dependency: reflection; move that to another jar released separately and just import it; generate a class or two with ASM (we do this to support Hibernate due to LGPL restrictions). Open to ideas. JAVA 11 We almost certainly would not be able to drop Java 8 support between TomEE 8.0.2 and the coming 8.0.3. More than likely we'd have to compile on Java 8 and then run the TCK tests on both Java 8 and Java 11 to verify all works. What that means is any support for Java 11 in the build itself is likely nice-to-have. This might become even less of a discussion if Java 8 becomes the primary java version for Jakarta EE 9, instead of simply being optional as it is now. This decision will be made by next Tuesday, but honestly given we're stuck with Java 8 due to TomEE 8/Jakarta EE 8, we're not really affected either way. Where I think that brings us is that we can do work to make the build run on Java 11 as long as it does not break the Java 8 build. Open to ideas and discussion on that. -- David Blevins http://twitter.com/dblevins http://www.tomitribe.com > On Jul 7, 2020, at 1:48 AM, Zowalla, Richard > <[email protected]> wrote: > > Hi, > > I was digging around the GitHub Repo and noticed PR 664 [1], which > tries to prepare TomEE to be build with JDK 11 but CORBA was removed in > JDK 11. > > There was a disucssion 2 years ago about removing CORBA related access > [2]. There even exist a JIRA (TOMEE-2324) for it [3]. > > If we want to build TomEE with JDK 11, we either need to (a) remove > CORBA dependencies (and check the implications as suggested in TOMEE- > 2324) or (b) add the CORBA API / IMPL back (e.g. via "jacorb" [4] or > via the glassfish api/impl ("glassfish-corba-orb" [5]). > > What is the plan for this? Any opinions? :) > > Best, > Richard > > > [1] https://github.com/apache/tomee/pull/664 > [2] https://www.mail-archive.com/[email protected]/msg08054.html > [3] https://issues.apache.org/jira/projects/TOMEE/issues/TOMEE-2324 > [4] https://www.jacorb.org/ > [5] https://javaee.github.io/glassfish-corba/
smime.p7s
Description: S/MIME cryptographic signature
