Details
-
Improvement
-
Status: Resolved
-
Minor
-
Resolution: Fixed
-
5.11.0
-
None
Description
The import ranges for the ActiveMQ client bundles should allow, not exclude version 2.0 of the javax.jms API, since JMS 2.0 is backwards compatible with 1.1.
This allows for ActiveMQ client jars to be used in runtimes with other JMS 2.0 clients.
Should be:
javax.jms;version=[1.1,2]
instead of:
javax.jms;version=[1.1,2)
Attachments
Issue Links
- is cloned by
-
AMQ-6506 OSGi import ranges for javax.jms should include version 2.0 for activemq-jms-pool
- Resolved