Changes between 2.x and 3.0.0

This is a major release that implements the JMS 3.0 specification, also known as Jakarta Messaging. As such, JMS Client 3.x is not compatible with 2.x: the API packages were renamed from javax.jms to jakarta.jms. It also requires Java 11, like JMS 3.0 does. See the JMS 3.0-related GitHub issue for more information.

JMS 3.0 users can now use RabbitMQ as a JMS backend, with the plain JMS 3.0 API or with higher-level layers like Spring 6.0.