[jira] [Created] (BROOKLYN-581) NoSuchMethodError occurs, when we use Brooklyn

[PandaMonkey (JIRA)]

PandaMonkey created BROOKLYN-581:


 Summary: NoSuchMethodError occurs, when we use Brooklyn
 Key: BROOKLYN-581
 URL: https://issues.apache.org/jira/browse/BROOKLYN-581
 Project: Brooklyn
  Issue Type: Bug
Affects Versions: 0.12.0
Reporter: PandaMonkey
 Fix For: 0.12.0


Hi, when we use org.apache.brooklyn:brooklyn-rest-client:0.12.0, our project 
get a NoSuchMethodError. The root cause is dependency conflict problem. By 
static analysis, we found that duplicate classes exist in different JARs, but 
they have different features, which leads to the really loaded classes are not 
the actually required ones of our project (JVM only load the classes present 
first on the classpath and shadow the other duplicate ones with the same name).

Conflicting Jar-pair: 


To avoid the other downstream projects encounter this conflicts, please pay 
attention about it. The conflicting info is listed below. Thanks!

 

Risk for 
jar-pair:
 Methods that only exist in javax.ws.rs:javax.ws.rs-api:2.0.1:: 
[neu.lab:findbug:0.0.1-SNAPSHOT:->org.apache.brooklyn:brooklyn-rest-client:0.12.0:->org.apache.brooklyn:brooklyn-rest-api:0.12.0:->javax.ws.rs:javax.ws.rs-api:2.0.1:]












 



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

[jira] [Updated] (BROOKLYN-581) NoSuchMethodError occurs, when we use Brooklyn

[PandaMonkey (JIRA)]

 [ 
https://issues.apache.org/jira/browse/BROOKLYN-581?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

PandaMonkey updated BROOKLYN-581:
-
Description: 
Hi, when we use org.apache.brooklyn:brooklyn-rest-client:0.12.0, our project 
get a *NoSuchMethodError*. The root cause is dependency conflict problem. By 
static analysis, we found that duplicate classes exist in different JARs, but 
they have different features, which leads to the really loaded classes are not 
the actually required ones of our project (JVM only load the classes present 
first on the classpath and shadow the other duplicate ones with the same name).

Conflicting Jar-pair: 


To avoid the other downstream projects encounter this conflicts, please pay 
attention about it. The conflicting info is listed below. Thanks!

 

Risk for 
jar-pair:
 Methods that only exist in javax.ws.rs:javax.ws.rs-api:2.0.1:: 
[neu.lab:findbug:0.0.1-SNAPSHOT:->org.apache.brooklyn:brooklyn-rest-client:0.12.0:->org.apache.brooklyn:brooklyn-rest-api:0.12.0:->javax.ws.rs:javax.ws.rs-api:2.0.1:]
 
 
 
 
 
 
 
 
 
 
 

 

  was:
Hi, when we use org.apache.brooklyn:brooklyn-rest-client:0.12.0, our project 
get a NoSuchMethodError. The root cause is dependency conflict problem. By 
static analysis, we found that duplicate classes exist in different JARs, but 
they have different features, which leads to the really loaded classes are not 
the actually required ones of our project (JVM only load the classes present 
first on the classpath and shadow the other duplicate ones with the same name).

Conflicting Jar-pair: 


To avoid the other downstream projects encounter this conflicts, please pay 
attention about it. The conflicting info is listed below. Thanks!

 

Risk for 
jar-pair:
 Methods that only exist in javax.ws.rs:javax.ws.rs-api:2.0.1:: 
[neu.lab:findbug:0.0.1-SNAPSHOT:->org.apache.brooklyn:brooklyn-rest-client:0.12.0:->org.apache.brooklyn:brooklyn-rest-api:0.12.0:->javax.ws.rs:javax.ws.rs-api:2.0.1:]












 


> NoSuchMethodError occurs, when we use Brooklyn
> --
>
> Key: BROOKLYN-581
> URL: https://issues.apache.org/jira/browse/BROOKLYN-581
> Project: Brooklyn
>  Issue Type: Bug
>Affects Versions: 0.12.0
>Reporter: PandaMonkey
>Priority: Major
> Fix For: 0.12.0
>
>
> Hi, when we use org.apache.brooklyn:brooklyn-rest-client:0.12.0, our project 
> get a *NoSuchMethodError*. The root cause is dependency conflict problem. By 
> static analysis, we found that duplicate classes exist in different JARs, but 
> they have different features, which leads to the really loaded classes are 
> not the actually required ones of our project (JVM only load the classes 
> present first on the classpath and shadow the other duplicate ones with the 
> same name).
> Conflicting Jar-pair: 
> 
> To avoid the other downstream projects encounter this conflicts, please pay 
> attention about it. The conflicting info is listed below. Thanks!
>  
> Risk for 
> jar-pair:
>  Methods that only exist in javax.ws.rs:javax.ws.rs-api:2.0.1:: 
> [neu.lab:findbug:0.0.1-SNAPSHOT:->org.apache.brooklyn:brooklyn-rest-client:0.12.0:->org.apache.brooklyn:brooklyn-rest-api:0.12.0:->javax.ws.rs:javax.ws.rs-api:2.0.1:]
>  
>  
>  
>   notEqual(java.util.Map,java.util.Map)>
>  
>  
>   notEqual(java.util.Collection,java.util.Collection)>
>  
>  
>  
>  
>  



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