Date: 2024-11-26
Present:
- Jared Anderson (IBM)
- Kyle Aure (IBM)
- Emily Jiang (IBM)
- Anand NK (IBM)
- Nathan Rauh (IBM)
- James Perkins (Red Hat)
- Ed Burns (MSFT)
- Scott Marlow (Red Hat)
- Petr Aubrecht (Payara)
- Brian Stansberry (Red Hat)
- Ivar Grimstad (Eclipse Foundation)
- John Clingan (Red Hat)
- Dmitry Kornilov (Oracle)
- Arjan Tijms (OmniFish)
- Gurunandan(Oracle)
- Jan Westerkamp (iJUG)
- Kenji Kazumura (Fujitsu)
Agenda and Minutes
Top of mind for Ed, Arjan, Jared
- Dec 3 is JakartaOne. We are canceling this meeting next week so people attend JakartaOne.
- Core profile status.
- Emily sent the Core Profile to ballot last week.
- Ballot will close December 4 unless all voters complete their vote early
- Ed asked, “Does anyone anticipate any controversy?”
- Emily did some whipping actions.
- Currently have 7 +1 votes.
- Need Oracle, Payara, TomiTribe.
- ACTION: Ed or Emily bring it up at the Spec Committee call.
- Let’s aim to close it during week 48.
- Confirmed sunset of Eclipse Forums (“ Eclipse IT update”) does not impact mail archives.
- JEA-483: Ballot among Platform Project committers regarding TCK exclusion list.
- Update from TCK project regarding “adding the @EJB annotation to all vehicles and updating the few application-client.xml descriptors to use the fixed lookup-name. Need to verify this work on glassfish.”
- Did this work?
- Marlow: Not yet as per comment https://github.com/eclipse-ee4j/glassfish/issues/25190#issuecomment-2501255470
- Arjan’s observation about the state of some non-appclient tests?
- “If other non-appclient tests are still failing or haven’t even been run yet, we may not be able to start the ballot anyway.”
- Need to understand a proposal that lets us get the Web Platform out in CY2024, let Platform Platform go to 2025
- ACTION: Ed to start [DISCUSS] thread about marking AppClient deprecated in EE 11 https://www.eclipse.org/lists/jakartaee-platform-dev/msg04586.html
Refactoring Progress Report
- Can we immediately prioritize the more important non-appclient tests, since we committed to having all of these running by 2024-12-15”
- Scott clarified that the “appclient” tests in question aren’t actually testing App Client itself, but use app client to call EJBs where (some of) the JPA tests are run.
Jakarta EE 11
- Authentication 3.1.1 TCK update
- Two new challenges opened with proposed PRs attached
- 3.1.1 TCK is staged, but not prompted yet. Would like to get these two challenges in and re-stage 3.1.1 to avoid having to do a 3.1.2 soon after 3.1.1
- Servlet 6.1.1 TCK update
- Latest staged version is from Oct 31
- What is the status of getting a newer staged version with the revert done?
- Validation 3.1 API
- Hearing that the Validation implementation cannot go final until some xml files are updated. I see in staging that the maven-metadata.xml files were updated yesterday for the validation API artifact to be different than what is in maven
- Maven metadata updates will be moved to maven soon?
Jakarta EE 12
The previous Agenda and minutes are below.
Date: 2024-11-19
Present:
- Ed Burns MSFT
- James Perkins (Red Hat)
- Jared Anderson (IBM)
- Kyle Aure (IBM)
- Anand NK (IBM)
- Nathan Rauh (IBM)
- Tom Watson (IBM)
- Ivar Grimstad (Eclipse Foundation)
- Dmitry Kornilov (Oracle)
- Scott Marlow (Red Hat)
- Emily Jiang (IBM)
- Gurunandan Rao(Oracle)
- Arjan Tijms (OmniFish)
- John Clingan (Red Hat)
- Matej Novotny (Red Hat)
- Kenji Kazumura (Fujitsu)
- Cesar Hernandez (TomitribE)
Agenda and Minutes
Top of mind for Ed, Arjan, Jared
- TCK
- https://github.com/eclipse-ee4j/glassfish/issues/25190
- Have work around that can be used to validate that there are no other issues with the app client tests.
- https://www.eclipse.org/lists/jakartaee-tck-dev/msg02114.html has three possible options (1-3) for moving forward
- Switch from “ejb-link” to “lookup-name” option 1
- Were there any lookup-name tests previously? Looks like we do have it in EJB tests.
- Reconsider how we run the Persistence tests on EE 11 implementations option 2
- Stay on the current path option 3
- It will be advantageous for another vendor to try these tests to see if they have the same problem with Wildfly for example
- Other vendors may be able to debug easier to determine what is wrong with the tests
- Still trying to find a fix though in glassfish it appears?
- https://github.com/jakartaee/platform-tck/issues/1624
- Tanya asked about status in general for where we are with web profile / platform before end of year completion
- TCK work is still happening in earnest
- Would like multiple vendors for ratification, but likely not able to be there by end of year
- Likely it is going to bleed into 2025, but how far into 2025 is the question
- There will be release activities that will be required once we have the TCK complete. CCR, javadoc, API, etc. Can do some of those things earlier to avoid the cost at the very end.
- Could do a shortcut, but would require a vote possibly by the platform specification committers, i.e. stop at some point and exclude tests that aren’t ready yet
- Core Profile release
- Scott Stark had some follow up actions to take after review from Emily which required a respin of the TCK
- Errant Java 11 reference in the TCK zip still. Looking to delay updating that into a future version of the TCK (version 12) and not require a respin
- Still waiting on getting an update to link to the implementations and not just the names of the implementations
- With these latest changes, the release review should be able to go to ballot by the end of the week.
- Certification requests updated to use the new TCK
Refactoring Progress Report
Jakarta EE 11
- Faces 4.1.1 TCK update
- Authentication 3.1.1 TCK update
- TCK isn’t published yet, but expect a new challenge from IBM this week that could possibly have a fix included into 3.1.1 so don’t need to do a 3.1.2 for the new challenge
- Servlet 6.1.1 TCK update
Jakarta EE 12
- Security manager removal: we mean it this time.
