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

Deal with ActiveMQ client moving to JMS 2.0 API, releasing both javax.jms and jakarta.jms variants #577

Open
jiridanek opened this issue Mar 26, 2023 · 0 comments · Fixed by #578
Open

Deal with ActiveMQ client moving to JMS 2.0 API, releasing both javax.jms and jakarta.jms variants #577

jiridanek opened this issue Mar 26, 2023 · 0 comments · Fixed by #578

Comments

@jiridanek
Copy link
Member

https://activemq.apache.org/jms2

Starting with activemq-client 5.18.0, JMS 2.0 interface library is required on the classpath.

Since we must maintain compatibility with what Red Hat releases in https://maven.repository.redhat.com/ga/org/apache/activemq/activemq-client/, which seems to be the 5.11.0 version, it seems best to stick to the latest JMS 1.1 and stop following upstream upgrades, unless anything changes.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
1 participant
@jiridanek