[
https://issues.apache.org/jira/browse/AMQ-5574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14313059#comment-14313059
]
James Carman commented on AMQ-5574:
-----------------------------------
You'd probably not want to go up to just 2. Most times folks do this:
[1.1,3)
Otherwise, if 2.0.1 was in the mix (assuming that would ever exist), you
wouldn't see it using "2]"
> 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
> Priority: Minor
>
> 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)
