Github user steveloughran commented on a diff in the pull request:
https://github.com/apache/spark/pull/6191#discussion_r30439495
--- Diff: pom.xml ---
@@ -705,7 +706,7 @@
<dependency>
<groupId>org.apache.curator</groupId>
<artifactId>curator-recipes</artifactId>
- <version>2.4.0</version>
+ <version>${curator.version}</version>
--- End diff --
that's what I meantioned as an extended patch, I do think it's the right
way to do it.
I've just pushed up a a new commit which declared the version of
`curator-framework` and `curator-client`, so they will always be consistent and
under the control of the spark build. It doesn't scope the new JARs, on the
basis that this POM is only setting the versions. They could be given the
hadoop.deps.scope though
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
