Tags 3.1 Milestone 1

[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

• [x] Service release branch created for N-1 release

I believe this is done with 3.x, but maybe it should be 3.0.x?

Will keep it as is for now, but we can always rename the branches later on.

• [x] New / master / main branch up-to-date with service release updates from previous version

New content in master that is new since 3.0, so I believe this right

• [x] If not done, move from master branch to main.

Code updates

• [x] Version update to the new version number including updating Export and Import versions in API jar’s MANIFEST.MF and Specification document
• [x] TCK brought over from platform repo if appropriate (do not delete from platform-tck repo until ratified)

This is at least started if not done

TCK code can found here: https://github.com/jakartaee/tags/tree/main/tck but it has not been deleted from the Platform. I created this issue for questions: https://github.com/jakartaee/platform-tck/issues/2500

• [x] Remove all tests from exclude list

I don't see any excluded tests. No-Op

• [x] Updates for the SEO change in the specification document as outlined in https://github.com/jakartaee/platform/issues/1108

See PR: https://github.com/jakartaee/tags/pull/282.

• [x] Do changes necessary to remove references to Java Security Manager from the spec and API as outlined in https://github.com/jakartaee/platform/issues/1018

not applicable

CI updates

• [x] OSSRH updates

See https://github.com/jakartaee/tags/pull/283

• [ ] 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.
• [ ] Jenkins job created for the new version for API, Javadoc, spec and TCK
• [ ] Make sure service stream Jenkins jobs are working for API and TCK

[volosied]

@pnicolucci @pnicolucci

Can either of you rename the master branch to main? I don't have permission. Are there also any jenkins or other build jobs that need to reference the new name?

[pnicolucci]

@pnicolucci @pnicolucci

Can either of you rename the master branch to main? I don't have permission. Are there also any jenkins or other build jobs that need to reference the new name?

I don't have permission either.

[pzygielo]

Can either of you rename the master branch to main? I don't have permission.

Create PR in https://github.com/jakartaee/.eclipsefdn

[pnicolucci]

https://github.com/jakartaee/.eclipsefdn/pull/14

[volosied]

Staging failed when I ran the jenkins build:

+ mvn -U -C -DskipTests -Ddoclint=none -Poss-release -Pstaging clean package gpg:sign install:install nexus-staging:deploy --batch-mode -Dorg.slf4j.simpleLogger.log.org.apache.maven.cli.transfer.Slf4jMavenTransferListener=warn
[INFO] Scanning for projects...
[INFO] Inspecting build with total of 1 modules
[INFO] Installing Central Publishing features
[WARNING] The requested profile "staging" could not be activated because it does not exist.
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time:  8.455 s
[INFO] Finished at: 2025-10-20T20:14:17Z
[INFO] ------------------------------------------------------------------------
[WARNING] The requested profile "staging" could not be activated because it does not exist.
[ERROR] No plugin found for prefix 'nexus-staging' in the current project and in the plugin groups [org.apache.maven.plugins, org.codehaus.mojo] available from the repositories [local (/home/jenkins/.m2/repository), eclipse.maven.central.mirror (https://repo.eclipse.org/content/repositories/maven_central/)] -> [Help 1]
[ERROR] 

I looked at websocket and saw the steps

# Deploy artifacts to snapshot repository
echo '-[ Deploy artifacts to snapshot repository ]-------------------------------------'
mvn -U -C \
    -DskipTests -Ddoclint=none \
    deploy gpg:sign \
    ${MVN_EXTRA}

I'll see what I can do.