[
https://issues.apache.org/jira/browse/QPIDJMS-568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17525626#comment-17525626
]
ASF subversion and git services commented on QPIDJMS-568:
---------------------------------------------------------
Commit 9dd92513c04a65335c8bde0bbbcf7ca6c8304225 in qpid-jms's branch
refs/heads/main from Robbie Gemmell
[ https://gitbox.apache.org/repos/asf?p=qpid-jms.git;h=9dd92513 ]
QPIDJMS-568: use jakarta.jms-api 3.0.0 spec dep for the client, i.e Jakarta
Messaging 3.0
- Make javax.jms -> jakarta.jms package import updates.
- Fix or remove broken tests as appropriate.
> Jakarta Messaging 3.0 support
> -----------------------------
>
> Key: QPIDJMS-568
> URL: https://issues.apache.org/jira/browse/QPIDJMS-568
> Project: Qpid JMS
> Issue Type: New Feature
> Components: qpid-jms-client
> Reporter: Robbie Gemmell
> Assignee: Robbie Gemmell
> Priority: Major
> Fix For: 2.0.0
>
>
> The jakarta.jms:jakarta.jms-api:3.0.0 / Jakarta Messaging 3.0 spec has been
> available for just over 18 months now, utilising the new _jakarta.jms_
> package namespace instead of the previous _javax.jms_ package namespace, as
> part of the wider package switch done then in Jakarta EE 9 and retained in
> the coming Jakarta EE 10.
> Usage of this is starting to see traction, with the Jakarta EE 9+ specs being
> used as the basis for various coming major framework etc releases, so it
> seems time to implement support of the newer APIs in order to allow use of
> the client with/by these going forward as well as other direct usages.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
