[ 
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)

Reply via email to