activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jean-Baptiste Onofré (JIRA) <j...@apache.org>
Subject [jira] [Commented] (AMQ-5574) OSGi import ranges for javax.jms should include version 2.0
Date Tue, 10 Feb 2015 12:54:22 GMT

    [ https://issues.apache.org/jira/browse/AMQ-5574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14314118#comment-14314118
] 

Jean-Baptiste Onofré commented on AMQ-5574:
-------------------------------------------

The version range could be:

{code}
[1.1,)
{code}

but it's "dangerous" if the JMS spec is not backward compliant.

As JMS 2.x is backward compatible, it's safer to do:

{code}
[1.1,3)
{code}

> 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: Jean-Baptiste Onofré
>            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)

Mime
View raw message