HADOOP-16765. Fix curator dependencies for gradle projects using hadoop-minicluster. #1763
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…op-minicluster. Gradle behaves differently than Maven when processing exclude rules through transitive dependencies. This causes gradle projects (e.g. in Kudu) that are using Hadoop MiniCluster to fail because different Guava version come to the classpath through Curator. In this fix we make sure that ZooKeeper, SLF4J and Gradle gets always excluded from Curator Client even if they would come through other Curator dependencies transitively.
|
💔 -1 overall
This message was automatically generated. |
goiri
reviewed
Dec 16, 2019
goiri
approved these changes
Dec 16, 2019
jojochuang
pushed a commit
to jojochuang/hadoop
that referenced
this pull request
Feb 2, 2020
… using hadoop-minicluster. (apache#1763) Gradle behaves differently than Maven when processing exclude rules through transitive dependencies. This causes gradle projects (e.g. in Kudu) that are using Hadoop MiniCluster to fail because different Guava version come to the classpath through Curator. In this fix we make sure that ZooKeeper, SLF4J and Gradle gets always excluded from Curator Client even if they would come through other Curator dependencies transitively. (cherry picked from commit 578bd10) Change-Id: I76ece08f3a951e7b3f8cb573b5bdb88dab218410
RogPodge
pushed a commit
to RogPodge/hadoop
that referenced
this pull request
Mar 25, 2020
…op-minicluster. (apache#1763) Gradle behaves differently than Maven when processing exclude rules through transitive dependencies. This causes gradle projects (e.g. in Kudu) that are using Hadoop MiniCluster to fail because different Guava version come to the classpath through Curator. In this fix we make sure that ZooKeeper, SLF4J and Gradle gets always excluded from Curator Client even if they would come through other Curator dependencies transitively.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Gradle behaves differently than Maven when processing exclude rules through transitive
dependencies. This causes gradle projects (e.g. in Kudu) that are using Hadoop MiniCluster
to fail because different Guava version come to the classpath through Curator. In this
fix we make sure that ZooKeeper, SLF4J and Gradle gets always excluded from Curator Client
even if they would come through other Curator dependencies transitively.