Jakarta EE Platform Call

Date: 2021-11-23

Present:

• Jan Westerkamp (iJUG)
• Jesse McConnell (Webtide)
• Ivar Grimstad (Eclipse Foundation)
• Tomas Langer (Oracle)
• Dmitry Kornilov (Oracle)
• John Clingan (Red Hat)
• Emily Jiang (IBM)
• Ed Bratt (Oracle)
• Roberto Cortez (Red Hat)
• Cesar Hernandez (Tomitribe)
• Tanja Obradovic (Eclipse Foundation)
• Rudy De Busscher (Payara)
• Scott Stark (Red Hat)

Agenda and Minutes

Jakarta EE 10 Status (standing agenda item)

• Interceptors 2.0.1 release needed
  • 2.1.0-RC1 was put out with SE 11 source/target
  • Revert back to commit: https://github.com/eclipse-ee4j/interceptor-api/commit/263f64cf484aead3c429c07dd69929d69c29377a and perform a 2.0.1 release
  • Emily will go forward with the release of 2.0.1
• Waves copied from 9.1 and updated
  • https://github.com/eclipse-ee4j/jakartaee-platform/pull/438
• https://docs.google.com/spreadsheets/d/1YTUpfdLZZrk2_UGwoX2w0seOCueRO3sQJIjWxpDAa7g/edit#gid=35969432
  • There are 3 specs that need mentor reviews to start

Voting on @Priority annotation proposal is out.

• Please cast your vote before 3rd Dec.
• Latest status shows that Option B2 and E is the most popular
• 23 votes in total so far
• Cast your vote if you haven’t done so yet
• All options can be reviewed in this Google Doc.
• The free version of Surveymonkey is causing some problems
• Look at using the EF SurveyMonkey in later surveys. Or something else? Google Forms is an option.

Jakarta Batch / CDI vote ongoing as well

• 40 responses can be accessed so far with a free account
• See this e-mail in jakarta.ee-community list for details about the Batch poll.

Jakarta namespace issue

• GroupId and ArtifactId for javax-versions and jakarta-versions are the same
• This cause problems for projects that need to use both

<groupId>jakarta.jms</groupId>
<artifactId>jms-api</artifactId>
<version>2.0.0</version> # javax-version
<version>3.0.0</version> #jakarta-version

• Proposed Solutions
  • Option 1: release a new official version of the javax-version to Maven Central (requires maven coordinate naming that prevent confusion)
  • Option 2: the project that needs it creates its own version of the api-jar (repackaging)
• Option 1 seems to be the most popular
• A naming convention should be defined
  • Avoid confusion
  • Avoid javax
  • Use a classifier?
  • Tomas will send a proposal on the mailing list

Initial committers for the Jakarta Commons project proposal are wanted!

• Google Doc with the proposal circulate on mailing lists(s)
  • https://docs.google.com/document/d/19eN3pQxtoMNoiqEKasPzbuTjUcYBC4pS0TGT12lVE3Y/edit?usp=sharing

Jakarta gRPC (working name) also looking for initial committers

A new specification for the Repository pattern is being discussed in Jakarta Persistence GitHub

• https://github.com/eclipse-ee4j/jpa-api/issues/294