Deliver interceptor-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

• 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.
• 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.
• 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.
• javax -> jakarta Spec updates
  If your component has Specification source, then all javax package references need to be updated to use jakarta package references.
• javax -> jakarta API updates
  Your component APIs need to move from using the javax namespace to using the jakarta namespace.
• 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.
• javax -> jakarta TCK updates
  Your component TCK needs to be updated to use the jakarta namespace.
• 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.
• 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.
• 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.
• 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:1]

[kwsutter]

Once we get a M1 or RC1 jar for the updated Interceptor API, could we post a notecard to the Milestone/RC column of the Project Board? It would help with other Projects dependent on Interceptors (Wave 1). Thanks!

[arjantijms]

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

[arjantijms]

Jakartified TCK in jakartaee/platform-tck@986c9e1

[arjantijms]

Jakartified implementation in eclipse-ee4j/glassfish@b8828e5 (and others)

[kwsutter]

One last request for the Specifications PR to promote the Milestone deliverables for this Project. The PR is created against the Jakarta EE specifications github repo. A template is automatically used when creating PRs against this repo which should help with understanding the steps required for a successful merge. We're not looking for perfection for this Milestone. We just want the ability to promote the great work that all of the Projects are doing.

If you submit a PR, please feel free to move this Epic to the Milestone 1 Ready column in the Project Board. Thanks!

[kwsutter]

Looking for an update on the status of the Interceptors Final Specification PR. If we're going to make the Sept deliverable goal, then this Wave 1 Specification needs to be ready for final ballot by Monday, July 19. Which means that the Specification PRs should already be created and under a "mentorship" review. Can I ask what the plans are for this Specification? Thanks!

[arjantijms]

Thanks to @thadumi the spec document is in a very good shape. I just pushed the proposed final API to staging:

https://jakarta.oss.sonatype.org/content/repositories/staging/jakarta/interceptor/jakarta.interceptor-api/2.0.0/

[arjantijms]

Spec & javadoc PR for review: jakartaee/specifications#233

[arjantijms]

Ballot thread: https://eclipse.org/lists/jakarta.ee-spec/msg01261.html

[arjantijms]

Release bug: https://bugs.eclipse.org/bugs/show_bug.cgi?id=568930

[arjantijms]

Completion steps completed: #82

I think this can be closed now.