There was a miscommunication with the EMO and there should not be any updates to the EFSL wording itself. I have closed the Issues where there was no activity. But, some of the Projects (including the Platform) have already made the requested changes. I’m checking with the EMO to see if these changes have to be reverted before Jakarta EE 9 completes.
Kevin is still working with the EMO (Wayne) to see if we have to revert anything for Jakarta EE 9. In the meantime, nothing is being requested of the Projects.
[Kevin] Jakarta EE 9 Specification PRs
Excellent progress on the creation and pre-reviewing of the PRs.
Trying to get some of the early ones through the ballot process, hopefully this week…
Everybody has access to the repo and can create/comment on PRs. Spec Committee members are required for checklists and merging.
Proposed resolution - Option F (recommendation from Spec Committee)
If you have an existing Automatic Module Name (MANIFEST) defined from Java EE 8 / Jakarta EE 8, update it to use the jakarta prefix. Do not create new Automatic Module Names for Jakarta EE 9. If you have an existing module-info.class defined from Java EE 8 / Jakarta EE 8, update it to use the jakarta prefix. Do not create new module-info.class files for Jakarta EE 9. If you have Nothing related to Module Names in your API, then leave it as-is.
Two actions - Update FAQ for Release Plan, and update Platform Spec with our direction for Module Names for Jakarta EE 9.
[BJ] Really need to test any Module Name definitions – thus another reason to wait until we have a JPMS strategy before introducing any new module names.
[cesar] Do we have any update for the issue mailing list search has? https://bugs.eclipse.org/bugs/show_bug.cgi?id=563173
Ivar will follow up when he gets back from vacation.
No additional agenda items were submitted, so we cut it off after 35 mins.