You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Gary Tully (JIRA)" <ji...@apache.org> on 2016/06/08 12:17:21 UTC
[jira] [Resolved] (AMQ-5574) OSGi import ranges for javax.jms
should include version 2.0
[ https://issues.apache.org/jira/browse/AMQ-5574?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gary Tully resolved AMQ-5574.
-----------------------------
Resolution: Fixed
Assignee: Gary Tully (was: Jean-Baptiste Onofré)
Fix Version/s: 5.14.0
fixed up the jms import in activemq-osgi such that it can pull in the 2.0 spec jar if necessary
> OSGi import ranges for javax.jms should include version 2.0
> -----------------------------------------------------------
>
> Key: AMQ-5574
> URL: https://issues.apache.org/jira/browse/AMQ-5574
> Project: ActiveMQ
> Issue Type: Improvement
> Components: OSGi/Karaf
> Affects Versions: 5.11.0
> Reporter: Matt Pavlovich
> Assignee: Gary Tully
> Priority: Minor
> Fix For: 5.14.0
>
>
> 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)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)