Jakarta EE Platform Call

Date: 2022-11-22

Present:

• Scott Marlow (Red Hat)
• Emily Jiang (IBM)
• Jan Westerkamp (iJUG)
• Ed Burns (Microsoft)
• Lukas Jungmann (Oracle)
• Scott Stark (Red Hat)
• Ivar Grimstad (Eclipse Foundation)
• BJ Hargrave (IBM)
• Ed Bratt (Oracle)
• Cesar Hernandez (Tomitribe)
• Brian Stansberry (Red Hat)
• Petr Aubrecht (Payara)
• -Werner Keil (Committer)
• Kenji Kazumura (Fujitsu)

Agenda and Minutes

Challenges (follow-up from last week)

• https://github.com/jakartaee/faces/issues/1715
• https://github.com/jakartaee/faces/issues/1716
• https://github.com/jakartaee/faces/issues/1717 (accepted)
• https://github.com/jakartaee/faces/issues/1718

• https://github.com/jakartaee/faces/issues/1722

• Discussion
  • No progress yet on these issues this week
  • Emily will follow up with Arjan to see how we can get them moving \

Certification Requests awaiting approval

• Issues · eclipse-ee4j/jakartaee-platform (github.com)

• Is there a way to automate?

  • Run action that validates
  • Can be hardcoded SHA values for each release
    • Or download the TCK zip and run sha256sum
  • Simple bash script?
  • Passed number of tests are not validated by us, that is the implementor’s responsibility
  • Create a wiki page that has the steps for validating, Ed and Ed will take care of this.

Relationship between Microprofile and Jakarta EE (based on the JWT discussion)

• Suggestion for general guiding principles

• Discussion summary
  • Differentiate between dependencies on individual specifications and profiles
  • Remove Principle b) since it is already covered by a)
  • Add principle for where to put new specifications
• Topic for further discussion:
  • Consider allowing MP specifications in Core Profile without namespace change

How to get TCK releases out and any committer should be able to do it

• Faces - Arjan will dig out the instruction

• Document the CI jobs in each github repo wiki
  • Create an issue in each specification project to request documentation for their TCK CI Jobs. Creat a couple to start with
  • Provide information about how to create a service release of their TCK
• Emily: Write a Google doc to document what we want to see in each project.
  • The document describes how to document the jobs on the project wiki
  • Establish a pattern/naming convention for CI jobs. Do we have a good example? MVC: Jakarta MVC - Dashboard [Jenkins] (eclipse.org)
  • Emily will put it in the shared drive
  • Nice to have versioning via folders, for example see https://ci.eclipse.org/jakartaee-tck/job/10/

• Scott: CDI has wiki to document CI

• Platform TCK wiki is out of date but is at https://github.com/eclipse-ee4j/jakartaee-tck/wiki/Jakarta-EE-TCK-Jenkins-jobs