Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Move to Jakarta Messaging 3.0.0 (from javax.jmx to jakarta.jms) #153

Merged
merged 12 commits into from
Nov 4, 2024
Merged

Move to Jakarta Messaging 3.0.0 (from javax.jmx to jakarta.jms) #153

merged 12 commits into from
Nov 4, 2024

Conversation

eolivelli
Copy link
Collaborator

@eolivelli eolivelli commented Oct 13, 2024 •
edited
Loading

This is a POC about moving to Jakarta Messaging 3.0.
Pulsar JMS is alrady compatible with Jakarta Messaging 2.x.

Contents of the patch:

  • move the package names of the API from javax.jms to jakarta.jms
  • require build on JDK11 (this is due to some ActiveMQ dependency)
  • bump the required dependencies to Jakarta Enterprise 9.x as required
  • upgrade Payra, Tomee and other containers to some version that runs Jakarta EE 9.x

TODOs:

  • Ensure that all of the examples work
  • Move the major version to Pulsar JMS 6.x

@mukesh-ctds mukesh-ctds changed the base branch from master to master-jakarta November 4, 2024 07:09
@mukesh-ctds mukesh-ctds changed the title Move to Jakarta Messaging 3.0.0 (from javax.jmx to jakarta.jms) - POC - DO NOT MERGE Move to Jakarta Messaging 3.0.0 (from javax.jmx to jakarta.jms) Nov 4, 2024
@mukesh-ctds mukesh-ctds merged commit 65e32a4 into master-jakarta Nov 4, 2024
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@eolivelli @mukesh-ctds