[jira] [Commented] (BEAM-3690) Dependency Conflict problems: several conflicting classes exist in different JARs (mockito-all/hamcrest-all)
[ https://issues.apache.org/jira/browse/BEAM-3690?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16369381#comment-16369381 ] Luke Cwik commented on BEAM-3690: - Now, all that is needed is to configure the maven enforcer plugin to ban hamcrest-all/mockito-all using [https://maven.apache.org/enforcer/enforcer-rules/bannedDependencies.html] This will prevent this issue from reoccurring. > 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] [Commented] (BEAM-3690) Dependency Conflict problems: several conflicting classes exist in different JARs
[ https://issues.apache.org/jira/browse/BEAM-3690?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16365088#comment-16365088 ] PandaMonkey commented on BEAM-3690: --- [~lcwik], thanks for your affirmation. I would like to contribute to BEAM. :)(*r) > 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: > 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] [Commented] (BEAM-3690) Dependency Conflict problems: several conflicting classes exist in different JARs
[ https://issues.apache.org/jira/browse/BEAM-3690?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16365085#comment-16365085 ] 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: > 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] [Commented] (BEAM-3690) Dependency Conflict problems: several conflicting classes exist in different JARs
[ https://issues.apache.org/jira/browse/BEAM-3690?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16364414#comment-16364414 ] Luke Cwik commented on BEAM-3690: - [~PandaMonkey], swapping to use mockito-core, hamcrest-core and hamcrest-library is the right thing to do. Feel free to open up a PR against the repository. It would also be nice if we banned these dependencies from the maven build, see [https://maven.apache.org/enforcer/enforcer-rules/bannedDependencies.html] for details. > 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 > > > 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] [Commented] (BEAM-3690) Dependency Conflict problems: several conflicting classes exist in different JARs
[ https://issues.apache.org/jira/browse/BEAM-3690?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16364352#comment-16364352 ] Kenneth Knowles commented on BEAM-3690: --- Related, but not the same: I have tried turning on dependency convergence in the maven enforcer plugin. We need the same for gradle to ensure long-term health and protect from regressions. Maybe the tool that generated this report can also fail the build? That would be nice. > 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 > > > 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] [Commented] (BEAM-3690) Dependency Conflict problems: several conflicting classes exist in different JARs
[ https://issues.apache.org/jira/browse/BEAM-3690?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16363864#comment-16363864 ] Ismaël Mejía commented on BEAM-3690: Mmm this seems like a handy report, [~PandaMonkey] is the tool you used to find this error public/open source ? I am curious to give it a try (also for other stuff). > 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 > > > 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] [Commented] (BEAM-3690) Dependency Conflict problems: several conflicting classes exist in different JARs
[ https://issues.apache.org/jira/browse/BEAM-3690?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16363396#comment-16363396 ] PandaMonkey commented on BEAM-3690: --- [~lcwik], Thx for your quick reply. To keep the consistency of dependencies in gradle and Maven, should I submit a pull request to use mockito-core instead of mockito-all in pom? > 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 > > > 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] [Commented] (BEAM-3690) Dependency Conflict problems: several conflicting classes exist in different JARs
[ https://issues.apache.org/jira/browse/BEAM-3690?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16361083#comment-16361083 ] Luke Cwik commented on BEAM-3690: - Note, the gradle build bans hamcrest-all and mockito-all and forces people to depend on hamcrest-core, mockito-core, ... So only fixes to Maven are required. > 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 > > > 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] [Commented] (BEAM-3690) Dependency Conflict problems: several conflicting classes exist in different JARs
[ https://issues.apache.org/jira/browse/BEAM-3690?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16361059#comment-16361059 ] Kenneth Knowles commented on BEAM-3690: --- Thanks for filing this. The SDK core does depend on Hamcrest core. It should not be including mockito or hamcrest-all. I will not be able to look at this right away - would you be willing to take a look? > 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)
