[jira] [Created] (APEXMALHAR-2556) When using the org.apache.apex:malhar-contrib:3.8.0, two conflictiing JARs are introduced in our project, which causes the "NoSuchMethodException" or "NoSuchMethodError" .

["PandaMonkey (JIRA)" <ji...@apache.org>]

PandaMonkey created APEXMALHAR-2556:
---------------------------------------

             Summary: When using the org.apache.apex:malhar-contrib:3.8.0, two conflictiing JARs are introduced in our project,  which causes the "NoSuchMethodException" or "NoSuchMethodError" .
                 Key: APEXMALHAR-2556
                 URL: https://issues.apache.org/jira/browse/APEXMALHAR-2556
             Project: Apache Apex Malhar
          Issue Type: Bug
    Affects Versions: 3.8.0
            Reporter: PandaMonkey
             Fix For: 3.9.0


Our project use *org.apache.apex:malhar-contrib:3.8.0*, two conflictiing JARs are introduced in our project,  which causes the "*NoSuchMethodException*" or "*NoSuchMethodError*" .

 Conflicting Jar-pair:<*org.apache.geronimo.specs:geronimo-jms_1.1_spec:1.1.1*:><*javax.jms:jms-api:1.1-rev-1:*>

By further analyzing the artifact bytecode, we found indeed duplicate classes with the same name exist in these two JARs. And the duplicate classes have different features, this is the main reason why our project crashed. So we provide the conflicting details as follows. Please notice this. Hope it can help you. Thanks.

Risk for jar-pair:<org.apache.geronimo.specs:geronimo-jms_1.1_spec:1.1.1:><javax.jms:jms-api:1.1-rev-1:>
 Methods that only exist in org.apache.geronimo.specs:geronimo-jms_1.1_spec:1.1.1:: [neu.lab:findbug:0.0.1-SNAPSHOT:->org.apache.apex:malhar-contrib:3.8.0:->org.apache.apex:malhar-library:3.8.0:->org.apache.activemq:activemq-client:5.8.0:->org.apache.geronimo.specs:geronimo-jms_1.1_spec:1.1.1:]
<javax.jms.QueueRequestor: javax.jms.TemporaryQueue getTemporaryQueue()>
<javax.jms.QueueRequestor: void setReceiver(javax.jms.QueueReceiver)>
<javax.jms.QueueRequestor: void setSender(javax.jms.QueueSender)>
<javax.jms.QueueRequestor: javax.jms.QueueSession getSession()>
<javax.jms.QueueRequestor: javax.jms.QueueSender getSender()>
<javax.jms.QueueRequestor: javax.jms.QueueReceiver getReceiver()>
<javax.jms.QueueRequestor: void setSession(javax.jms.QueueSession)>
<javax.jms.QueueRequestor: void setTemporaryQueue(javax.jms.TemporaryQueue)>
<javax.jms.TopicRequestor: void setSession(javax.jms.TopicSession)>
<javax.jms.TopicRequestor: void setTopic(javax.jms.Topic)>
<javax.jms.TopicRequestor: void setPublisher(javax.jms.TopicPublisher)>
<javax.jms.TopicRequestor: javax.jms.TopicSubscriber getSubscriber()>
<javax.jms.TopicRequestor: javax.jms.Topic getTopic()>
<javax.jms.TopicRequestor: void setSubscriber(javax.jms.TopicSubscriber)>
<javax.jms.TopicRequestor: javax.jms.TopicPublisher getPublisher()>
<javax.jms.TopicRequestor: javax.jms.TopicSession getSession()>
<javax.jms.TopicRequestor: void setTemporaryTopic(javax.jms.TemporaryTopic)>
<javax.jms.TopicRequestor: javax.jms.TemporaryTopic getTemporaryTopic()>

 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)