Merging jakarta Messaging 3.0.0 (from javax.jmx to jakarta.jms) changes into the master branch #155
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
* Switch to Jakarta Messaging 3.0 and jakarta.jms package * Fix build * Upgrade TCK to Jakarta Messaging TCK 3.0.1 * Fix TCK CI * Upgrade more references to jakarta.xxx * Add legacy javax.annotation api * Fix TCK Executor * Fix version and add rerun failed tests * Disable failing test * Fix for spring application * Updated brokerServiceUrl to spring application * Revert of jakarta.annotation-api to javax.annotation-api --------- Co-authored-by: mukesh-ctds <[email protected]>
srinath-ctds
approved these changes
Nov 19, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR includes:
Merging this PR to master.
Going forward we need to maintain 2 branches. One for jakarta which will be on master branch & for javax the branch will be branch-6.0.