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.

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

Support for Jakarta Messaging #2989

Closed
sebastian-alfers opened this issue Jul 3, 2023 · 0 comments
Closed

Support for Jakarta Messaging #2989

sebastian-alfers opened this issue Jul 3, 2023 · 0 comments
Assignees
Labels
Milestone

Comments

@sebastian-alfers
Copy link
Contributor

sebastian-alfers commented Jul 3, 2023

Instead or in addition to the existing javax based JMS implementation, use jakarta.

Scala3 support would be great to have as well.

Refs

@ennru ennru changed the title Support for jakarta Support for Jakarta Messaging Jul 7, 2023
@ennru ennru added the p:jms label Jul 7, 2023
@patriknw patriknw self-assigned this Nov 29, 2023
patriknw added a commit that referenced this issue Nov 30, 2023
* Converted from Alpakka JMS
* Jakarta Messaging 3.1
* jakarta.jms package instead of javax.jms
patriknw added a commit that referenced this issue Dec 1, 2023
* Converted from Alpakka JMS
* Jakarta Messaging 3.1
* jakarta.jms package instead of javax.jms
* fix: close sessions on connection loss, #3041
* add to autolabeler and check-build-test
* sort build projects
* extensive rewrite of tests to use ActiveMQ Artemis
  * because support for Jakarta Messaging was addd in ActiveMQ 6.0,
    which requires JDK 17
* Text improvements
  * ActiveMQ Artemis doc adjustments

---------

Co-authored-by: Enno <458526+ennru@users.noreply.github.com>
@patriknw patriknw added this to the 7.0.1 milestone Dec 1, 2023
@patriknw patriknw closed this as completed Dec 1, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants