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

• Type: Bug
• Status: Resolved
• Priority: P3
• Resolution: Fixed
• Affects Version/s: 2.2.0
• Fix Version/s: 2.4.0
• Component/s: sdk-java-core
• Labels: Done
• Assignee: PandaMonkey
• Reporter: PandaMonkey
• Created: 12/Feb/18 08:27
• Updated: 06/Oct/20 21:55
• Resolved: 23/Feb/18 14:40

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:<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.

 

Issue Links

• links to: GitHub Pull Request #4690
• links to: GitHub Pull Request #4706
• links to: GitHub Pull Request #4712