Deliver Jakarta Messaging 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) Github issue created here: #266
• [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 - #268 JMS 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! [wave:0]

[smillidge]

OpenMQ is now in the jakarta namespace so you can tick the CI checkbox.

[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!

[arjantijms]

Spec PRs done:

• https://github.com/jakartaee/specifications/pull/201
• https://github.com/jakartaee/specifications/pull/202

[edbratt]

I sent e-mail with a similar message: Would it be helpful if I were to go ahead and update the base information in the TCK User Guide, Readme, and Release Notes for Jakarta Messaging? We'd still need the API team to review that content, but I could do most of the clerical updates in the TCK project. Let me know if that would be useful. This work could be considered part of https://github.com/eclipse-ee4j/jakartaee-tck/issues/384

[dblevins]

That would of course be incredibly welcome and useful. There's still heavy lifting to do on EJB, so any help with messaging is more than fantastic.

On Aug 6, 2020, at 2:39 PM, Ed Bratt notifications@github.com wrote:

I sent e-mail with a similar message: Would it be helpful if I were to go ahead and update the base information in the TCK User Guide, Readme, and Release Notes for Jakarta Messaging. We'd still need the API team to review that content, but I could do most of the clerical updates in the TCK project. Let me know if that would be useful. This work could be considered part of eclipse-ee4j/jakartaee-tck#384 https://github.com/eclipse-ee4j/jakartaee-tck/issues/384 — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/eclipse-ee4j/jms-api/issues/255#issuecomment-670205277, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAAXFTWGP5APGJ6OQNCCT43R7MPIVANCNFSM4KGUGI2Q.

[edbratt]

I believe that the TCK documentation has been updated for Jakarta Messaging 3.0. This is available in the latest builds, here.

[arjantijms]

Ballot succesfull: https://eclipse.org/lists/jakarta.ee-spec/msg01298.html

[arjantijms]

As Jakarta Messaging has been delivered, I'm closing this. Thanks to everyone involved!