Deliver common-annotations-api Specification Version update for Jakarta EE 9

[kwsutter]

Is your feature request related to a problem? Please describe. Jakarta EE 9 is the next major release, with the main focus of moving from the javax namespace to the jakarta namespace.

Describe the solution you'd like This issue will be used to track the progress of this work effort via the Jakarta EE 9 Project board.

Additional context Jakarta EE Specification Process Eclipse Project Handbook Eclipse Release Record for Jakarta EE 9

ToDo

• [x] Create Eclipse Release Record in your respective Jakarta Specification Project. Most Component Release Records will just reference the Jakarta EE 9 Platform Release Plan. But, if your Component deviates at all from the Platform Release Plan, then a description of the changes will be required in the Release Record.
• [x] Initiate a ballot for your Jakarta Release Record/Plan. Again, if your component is only doing the required minimum as defined by the Jakarta EE 9 Platform Release Plan, then no separate ballot is required. You are already approved. But, if your component deviates from the Platform Release Plan, then you will need to initiate your own ballot as defined by the Jakarta EE Specification Process.
• [x] Jakarta-ize your Specification document (if applicable) Many of the Jakarta EE components now have the source for their Specification documents. It is strongly recommended that these Specification documents are properly updated to represent Jakarta EE instead of Java EE. Some helpful instructions are documented here.
• [x] javax -> jakarta Spec updates If your component has Specification source, then all javax package references need to be updated to use jakarta package references.
• [x] javax -> jakarta API updates Your component APIs need to move from using the javax namespace to using the jakarta namespace.
• [x] Release Candidate (RC) of Jakarta API in Maven Central A Release Candidate of your component API should be pushed to Maven Central as soon as humanly possible. This will allow other dependent components to utilize your APIs as they are updating their APIs. Multiple revisions of these Release Candidate APIs are allowed (and probably expected) during the development cycle.
• [x] javax -> jakarta TCK updates Your component TCK needs to be updated to use the jakarta namespace.
• [x] javax -> jakarta Compatible Implementation updates Your compatible implementation that will be used to demonstrate completeness of the Specification needs to be updated to use the jakarta namespace.
• [x] Final Jakarta API available in Staging Repo When ready, your final version of the API needs to be staged to get ready for the PR review and approvals.
• [x] Draft Specification and Apidoc PRs ready for review Like we did for Jakarta EE 8, draft PRs need to be created and reviewed in preparation for the final ballots.
• [x] Release Review Ballot started Each Jakarta EE component will need to initiate a separate Release Review ballot after proper reviewing has completed. To be clear, there will not be a blanket Release Review for all of Jakarta EE 9 like we did for the Plan Review. Each component needs a separate Release Review.

[kwsutter]

Can I ask this team to please create and assign the following labels to this Issue? Thank you! [Epic] [wave:0]

[m0mus]

https://repo1.maven.org/maven2/jakarta/annotation/jakarta.annotation-api/2.0.0-RC1/

[arjantijms]

@m0mus the parent pom has not been published. This means the RC1 dependency can't be used now. See also https://github.com/eclipse-ee4j/common-annotations-api/issues/73

[m0mus]

Yes. We will fix it soon.

[Emily-Jiang]

I am trying to figure out where the annotation tcks live. I looked at the whole tck dir. I cannot locate where annotation tcks are. Any ideas @m0mus ?

[m0mus]

@Emily-Jiang Jakarta Annorartions is just a set of annorartions, so there are no TCKs, just a signature test.

[thadumi]

@Emily-Jiang Jakarta Annorartions is just a set of annorartions, so there are no TCKs, just a signature test.

So wouldn't it be better to mark it as unnecessary on the list?

[edbratt]

The Signature test is part of the TCK so I would phrase this as: a TCK is required, it only contains a signature test. Jakarta EE 8 has an annotations TCK. Jakarta EE 9 should have an equivalent TCK should be generated and should be v 2.x in my opinion (and a nightly does, in fact exist: annotations-tck-2.0.0.zip)

[kwsutter]

Moved to Wave 1 deliverable due to the downstream dependencies for implementations and testing.

[keilw]

@kwsutter, @m0mus please review my PR, it helps fix the module definition for Jakarta Annotations also in the README file.