PandaMonkey commented on BEAM-3690:

[~kenn], [~iemejia] thanks for your interest about our tool. The conflict 
detection tool is in the development and evaluation phase. I'm so honored to 
help open source project to ensure long-term health and protect from 
regressions. You are welcome to try it when we release it later!

> 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.3.0
>         Attachments: beam_conflicts.txt
>          Time Spent: 10m
>  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:<org.mockito:*mockito-all*:1.9.5:><org.hamcrest:*hamcrest-all*:1.3:>
> 2. 
> jar-pair:<org.mockito:*mockito-all*:1.9.5:><org.hamcrest:*hamcrest-core*:1.3:>
> 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

Reply via email to