[ 
https://issues.apache.org/jira/browse/ARTEMIS-2557?focusedWorklogId=360445&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-360445
 ]

ASF GitHub Bot logged work on ARTEMIS-2557:
-------------------------------------------

                Author: ASF GitHub Bot
            Created on: 16/Dec/19 19:29
            Start Date: 16/Dec/19 19:29
    Worklog Time Spent: 10m 
      Work Description: asfgit commented on pull request #2898: ARTEMIS-2557 
don't export openwire-protocol JMS spec dep
URL: https://github.com/apache/activemq-artemis/pull/2898
 
 
   
 
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
[email protected]


Issue Time Tracking
-------------------

    Worklog Id:     (was: 360445)
    Time Spent: 2.5h  (was: 2h 20m)

> Don't export openwire-protocol JMS spec dependency
> --------------------------------------------------
>
>                 Key: ARTEMIS-2557
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-2557
>             Project: ActiveMQ Artemis
>          Issue Type: Task
>          Components: Broker, OpenWire
>    Affects Versions: 2.10.1
>            Reporter: SL
>            Assignee: Justin Bertram
>            Priority: Minor
>          Time Spent: 2.5h
>  Remaining Estimate: 0h
>
> artemis-openwire-protocol has a dependency on geronimo-jms-1.1_spec
> {code:xml}
>        <dependency>
>          <groupId>org.apache.geronimo.specs</groupId>
>          <artifactId>geronimo-jms_1.1_spec</artifactId>
>          <version>1.1.1</version>
>       </dependency>
> {code}
> However other components such as artemis-jms-server have a dependency on 
> geronimo-jms_2.0_spec which carry a superset of the same interfaces, but with 
> subtle differences (such as the JMSContext in ConnectionFactory)
> If your have both components in a dependency hierarchy you may end up with a 
> classpath including both jar which can lead to a behavior that is
> a) inconsistent, since one or the other jar may have been loaded first to 
> resolve a given interface
> b) funny, if a component compiled against an interface from 2.0 try to use 
> one from 1.1.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to