JSON Binding 3.1 Milestone 2

[jhanders34]

For Milestone 1, if possible it would be ideal to complete the following minimum actions. Milestone 1 work should be completed by October 15 including API, Javadoc, and specification doc artifacts being available. Ideally there would also be a Milestone version of the TCK as well. Status for the Milestone 1 issues will be tracked using this dashboard.

GitHub updates

• Service release branch created for N-1 release
• New / master / main branch up-to-date with service release updates from previous version
• If not done, move from master branch to main. update: jakarta jsonb repo to use main .eclipsefdn#25

Code updates

• Version update to the new version number including updating Export and Import versions in API jar’s MANIFEST.MF and Specification document fix: bundle manifest 3.1.0 #388
• TCK brought over from platform repo if appropriate (do not delete from platform-tck repo until ratified)
• Remove all tests from exclude list
• Updates for the SEO change in the specification document as outlined in Make specifications more discoverable by search engines and AI platform#1108
• Do changes necessary to remove references to Java SecurityManager from the spec and API as outlined in Remove Security Manager Dependency Across Platform platform#1018
• No changes identified

CI updates

• OSSRH updates
  • Stage and Release to Maven Central builds: https://ci.eclipse.org/jsonb/view/Release%20Builds/
  • Pull, Stage, and Promote to Eclipse.org: https://ci.eclipse.org/jsonb/view/Eclipse%20Builds/
• TCK running with EE 11 ratifying implementation with Java 21 (tests could be failing due to new tests added / excluded tests no longer removed) and any other LTS versions supported by your new version. Bonus points for Java 25 running.
  • build: allow pipeline to run against staged TCK eclipse-ee4j/yasson#711
• Jenkins job created for the new version for API, Javadoc, spec and TCK
  • Not necessary, Jenkins jobs work both with service and release streams.
• Make sure service stream Jenkins jobs are working for API and TCK: fix: update service branch to use new parent pom #386