[jira] [Updated] (BEAM-3690) Dependency Conflict problems: several conflicting classes exist in different JARs (mockito-all/hamcrest-all)

2018-02-19 Thread Luke Cwik (JIRA) 

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

Luke Cwik updated BEAM-3690:

Priority: Minor  (was: Major)

> Dependency Conflict problems: several conflicting classes exist in different 
> JARs (mockito-all/hamcrest-all)
> 
>
> Key: BEAM-3690
> URL: https://issues.apache.org/jira/browse/BEAM-3690
> Project: Beam
>  Issue Type: Bug
>  Components: sdk-java-core
>Affects Versions: 2.2.0
>Reporter: PandaMonkey
>Assignee: PandaMonkey
>Priority: Minor
> Fix For: 2.4.0
>
> Attachments: beam_conflicts.txt
>
>  Time Spent: 1.5h
>  Remaining Estimate: 0h
>
> Hi, we found that there are duplicate classes exist in different JARs, and 
> these classes have different features.
> The conflicting JAR pairs are:
> 1. 
> jar-pair:
> 2. 
> jar-pair:
> Some of method only exist in one version of duplicate classes.
> As the JVM only load the classes present first on the classpath and shadow 
> the other duplicate ones with the same names. The dependency conflict problem 
> brings high risks of "*NoSuchMethodException*" or "*NoSuchMethodError*"  
> issues at runtime. The conflicting details are listed in the attachment. 
> Please notice that. Thanks.
>  



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

[jira] [Updated] (BEAM-3690) Dependency Conflict problems: several conflicting classes exist in different JARs (mockito-all/hamcrest-all)

2018-02-19 Thread Luke Cwik (JIRA) 

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

Luke Cwik updated BEAM-3690:

Summary: Dependency Conflict problems: several conflicting classes exist in 
different JARs (mockito-all/hamcrest-all)  (was: Dependency Conflict problems: 
several conflicting classes exist in different JARs)

> Dependency Conflict problems: several conflicting classes exist in different 
> JARs (mockito-all/hamcrest-all)
> 
>
> Key: BEAM-3690
> URL: https://issues.apache.org/jira/browse/BEAM-3690
> Project: Beam
>  Issue Type: Bug
>  Components: sdk-java-core
>Affects Versions: 2.2.0
>Reporter: PandaMonkey
>Assignee: PandaMonkey
>Priority: Major
> Fix For: 2.4.0
>
> Attachments: beam_conflicts.txt
>
>  Time Spent: 1.5h
>  Remaining Estimate: 0h
>
> Hi, we found that there are duplicate classes exist in different JARs, and 
> these classes have different features.
> The conflicting JAR pairs are:
> 1. 
> jar-pair:
> 2. 
> jar-pair:
> Some of method only exist in one version of duplicate classes.
> As the JVM only load the classes present first on the classpath and shadow 
> the other duplicate ones with the same names. The dependency conflict problem 
> brings high risks of "*NoSuchMethodException*" or "*NoSuchMethodError*"  
> issues at runtime. The conflicting details are listed in the attachment. 
> Please notice that. Thanks.
>  



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

[jira] [Updated] (BEAM-3690) Dependency Conflict problems: several conflicting classes exist in different JARs

2018-02-19 Thread JIRA 

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

Jean-Baptiste Onofré updated BEAM-3690:
---
Fix Version/s: (was: 2.3.0)
   2.4.0

> Dependency Conflict problems: several conflicting classes exist in different 
> JARs
> -
>
> Key: BEAM-3690
> URL: https://issues.apache.org/jira/browse/BEAM-3690
> Project: Beam
>  Issue Type: Bug
>  Components: sdk-java-core
>Affects Versions: 2.2.0
>Reporter: PandaMonkey
>Assignee: PandaMonkey
>Priority: Major
> Fix For: 2.4.0
>
> Attachments: beam_conflicts.txt
>
>  Time Spent: 40m
>  Remaining Estimate: 0h
>
> Hi, we found that there are duplicate classes exist in different JARs, and 
> these classes have different features.
> The conflicting JAR pairs are:
> 1. 
> jar-pair:
> 2. 
> jar-pair:
> Some of method only exist in one version of duplicate classes.
> As the JVM only load the classes present first on the classpath and shadow 
> the other duplicate ones with the same names. The dependency conflict problem 
> brings high risks of "*NoSuchMethodException*" or "*NoSuchMethodError*"  
> issues at runtime. The conflicting details are listed in the attachment. 
> Please notice that. Thanks.
>  



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

[jira] [Updated] (BEAM-3690) Dependency Conflict problems: several conflicting classes exist in different JARs

2018-02-12 Thread PandaMonkey (JIRA) 

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

PandaMonkey updated BEAM-3690:
--
Description: 
Hi, we found that there are duplicate classes exist in different JARs, and 
these classes have different features.

The conflicting JAR pairs are:

1. jar-pair:

2. 
jar-pair:

Some of method only exist in one version of duplicate classes.

As the JVM only load the classes present first on the classpath and shadow the 
other duplicate ones with the same names. The dependency conflict problem 
brings high risks of "*NoSuchMethodException*" or "*NoSuchMethodError*"  issues 
at runtime. The conflicting details are listed in the attachment. Please notice 
that. Thanks.

 

  was:
Hi, we found that there are duplicate classes exist in different JARs, and 
these classes have different features. As the JVM only load the classes present 
first on the classpath and shadow the other duplicate ones with the same names. 
The dependency conflict problem brings high risks of "*NoSuchMethodException*" 
or "*NoSuchMethodError*"  issues at runtime. The conflicting details are listed 
in the attachment. Please notice that. Thanks.

 


> Dependency Conflict problems: several conflicting classes exist in different 
> JARs
> -
>
> Key: BEAM-3690
> URL: https://issues.apache.org/jira/browse/BEAM-3690
> Project: Beam
>  Issue Type: Bug
>  Components: sdk-java-core
>Affects Versions: 2.2.0
>Reporter: PandaMonkey
>Assignee: Kenneth Knowles
>Priority: Major
> Fix For: 2.3.0
>
> Attachments: beam_conflicts.txt
>
>
> Hi, we found that there are duplicate classes exist in different JARs, and 
> these classes have different features.
> The conflicting JAR pairs are:
> 1. 
> jar-pair:
> 2. 
> jar-pair:
> Some of method only exist in one version of duplicate classes.
> As the JVM only load the classes present first on the classpath and shadow 
> the other duplicate ones with the same names. The dependency conflict problem 
> brings high risks of "*NoSuchMethodException*" or "*NoSuchMethodError*"  
> issues at runtime. The conflicting details are listed in the attachment. 
> Please notice that. Thanks.
>  



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

[jira] [Updated] (BEAM-3690) Dependency Conflict problems: several conflicting classes exist in different JARs

2018-02-12 Thread PandaMonkey (JIRA) 

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

PandaMonkey updated BEAM-3690:
--
Description: 
Hi, we found that there are duplicate classes exist in different JARs, and 
these classes have different features. As the JVM only load the classes present 
first on the classpath and shadow the other duplicate ones with the same names. 
The dependency conflict problem brings high risks of "*NoSuchMethodException*" 
or "*NoSuchMethodError*"  issues at runtime. The conflicting details are listed 
in the attachment. Please notice that. Thanks.

 

  was:
Hi, we found that there are duplicate classes exist in different JARs, and 
these classes have different features. As the JVM only load the classes present 
first on the classpath and shadow the other duplicate ones with the same names. 
The dependency conflict problem brings high risks of "*NoSuchMethodException*" 
or "*NoSuchMethodError*"  issues at runtime. The conflicting details are listed 
in the attachment. Please notice that.

 


> Dependency Conflict problems: several conflicting classes exist in different 
> JARs
> -
>
> Key: BEAM-3690
> URL: https://issues.apache.org/jira/browse/BEAM-3690
> Project: Beam
>  Issue Type: Bug
>  Components: sdk-java-core
>Affects Versions: 2.2.0
>Reporter: PandaMonkey
>Assignee: Kenneth Knowles
>Priority: Major
> Fix For: 2.3.0
>
> Attachments: beam_conflicts.txt
>
>
> Hi, we found that there are duplicate classes exist in different JARs, and 
> these classes have different features. As the JVM only load the classes 
> present first on the classpath and shadow the other duplicate ones with the 
> same names. The dependency conflict problem brings high risks of 
> "*NoSuchMethodException*" or "*NoSuchMethodError*"  issues at runtime. The 
> conflicting details are listed in the attachment. Please notice that. Thanks.
>  



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

[jira] [Updated] (BEAM-3690) Dependency Conflict problems: several conflicting classes exist in different JARs

2018-02-12 Thread PandaMonkey (JIRA) 

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

PandaMonkey updated BEAM-3690:
--
Attachment: beam_conflicts.txt

> Dependency Conflict problems: several conflicting classes exist in different 
> JARs
> -
>
> Key: BEAM-3690
> URL: https://issues.apache.org/jira/browse/BEAM-3690
> Project: Beam
>  Issue Type: Bug
>  Components: sdk-java-core
>Affects Versions: 2.2.0
>Reporter: PandaMonkey
>Assignee: Kenneth Knowles
>Priority: Major
> Fix For: 2.3.0
>
> Attachments: beam_conflicts.txt
>
>
> Hi, we found that there are duplicate classes exist in different JARs, and 
> these classes have different features. As the JVM only load the classes 
> present first on the classpath and shadow the other duplicate ones with the 
> same names. The dependency conflict problem brings high risks of 
> "*NoSuchMethodException*" or "*NoSuchMethodError*"  issues at runtime. The 
> conflicting details are listed in the attachment. Please notice that.
>  



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