You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Robbie Gemmell (Jira)" <ji...@apache.org> on 2022/09/16 11:49:00 UTC

[jira] [Updated] (QPIDJMS-571) update to jakarta.jms-api 3.1.0 / Jakarta Messaging 3.1

     [ https://issues.apache.org/jira/browse/QPIDJMS-571?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Robbie Gemmell updated QPIDJMS-571:
-----------------------------------
    Issue Type: New Feature  (was: Task)

> update to jakarta.jms-api 3.1.0 / Jakarta Messaging 3.1
> -------------------------------------------------------
>
>                 Key: QPIDJMS-571
>                 URL: https://issues.apache.org/jira/browse/QPIDJMS-571
>             Project: Qpid JMS
>          Issue Type: New Feature
>          Components: qpid-jms-client
>            Reporter: Robbie Gemmell
>            Assignee: Robbie Gemmell
>            Priority: Major
>             Fix For: 2.1.0
>
>
> QPIDJMS-568 introduced Jakarta Messaging 3.0 support, i.e use of the jakarta.jms-api 3.0.0 API dependency, using the jakarta.jms api package rather than prior javax.jms. The jakarta.jms-api 3.1.0 / Jakarta Messaging 3.1 artifacts (for use in Jakarta EE 10) have been staged for a few months but have now been released, we should update.
> There are no changes of any particular effect. It now requires Java 11, which we already did. Updates some annotations we dont use. Adds some new exception constructors which simplify passing the linked exception, which we already did the old way and wont use to remain compatible with the older API artifact for now.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org