Skip to main content

Jakarta EE Platform Project

Home for the Jakarta EE Platform Team

Jakarta EE Platform Call

Date: 2020-06-16

Present:

  • Kevin Sutter (IBM)
  • Ivar Grimstad (Eclipse Foundation)
  • BJ Hargrave (IBM)
  • Andy McCright(IBM)
  • Scott Marlow (Red Hat)
  • Steve Millidge (Payara)
  • Nitin Dahyabhai (WTP)
  • Dmitry Kornilov (Oracle)
  • Ed Bratt (Oracle)
  • Emily Jiang (IBM)
  • Paul Nicolucci (IBM)
  • Nathan Erwin (Individual)
  • Tanja Obradovic (Eclipse Foundation)
  • Alessio Soldano (Red Hat)
  • Scott Stark (Red Hat)

Agenda

Milestone 1 Status - Looking good! [KWS]

  • Overall Project Board for Jakarta EE 9
    • https://github.com/orgs/eclipse-ee4j/projects/17#column-9442495
  • Platform Spec and API RC2 PR
    • https://github.com/jakartaee/specifications/pull/180
    • https://deploy-preview-180–jakartaee-specifications.netlify.app/specifications/platform/9/
  • Web Profile Spec and API RC2 PR
    • https://github.com/jakartaee/specifications/pull/179
    • https://deploy-preview-179–jakartaee-specifications.netlify.app/specifications/webprofile/9/
  • Glassfish 6.0.0-M1 (Steve)
    • Considered ready for Milestone deliverable
    • Staged for both Platform and Web Profile, ready to push to Maven
    • Can respin an M2, if absolutely necessary
  • Platform TCK 9.0.0-M1 (Scott)
    • Around Platform TCK 37% passing
    • Around 93% of Platform TCK sourced Standalone TCKs
    • Summary, we are not compatible yet.
    • Intent is to deliver a milestone Platform TCK
  • Goal of Thursday, June 18 as the “push to Maven” date
    • Platform and Web Profile 9.0.0-RC2 APIs
    • Glassfish 6.0.0-M1
    • Platform TCK 9.0.0-M1 (not pushed to Maven)
      • https://download.eclipse.org/ee4j/jakartaee-tck/jakartaee9/milestone/jakartaeetck-9.0.0-M1.zip

What is the goal for backward compatibility of < 9 applications [Ed]

  • Where do we document what happens to legacy applications?
  • Do we need to document the old to new mappings?
    • XSDs?
    • SPEC API Classes?
    • Spec names?
    • Property name mappings?
  • Add migration guide or single central document?
    • Probably create a folder in Platform git repo
    • BJ recommends a separate repo since it could be used as a sub-project within another repo. (Suggestion - jakartaee-renames as repo name)
    • https://bugs.eclipse.org/bugs/show_bug.cgi?id=564345
  • Possibly use a properties file as input to the migration guide. This could then be used directly by the Transformer or any other “stack product” tools.
  • Nominate BJ for Platform project.

Back to the top