Github user steveloughran commented on the issue:
https://github.com/apache/spark/pull/17834
I've just pushed up an update which changes the module name; tested in
maven and SBT; hadoop cloud JAR dependencies pulled down.
A JAR is created, it's just a stub one. As a result, when you build the
assembly with -Phadoop-cloud, you get something from spark mixed in with the
hadoop modules
```
assembly/target/scala-2.11/jars/hadoop-aws-2.7.3.jar
assembly/target/scala-2.11/jars/hadoop-azure-2.7.3.jar
assembly/target/scala-2.11/jars/hadoop-client-2.7.3.jar
assembly/target/scala-2.11/jars/hadoop-cloud_2.11-2.3.0-SNAPSHOT.jar
assembly/target/scala-2.11/jars/hadoop-common-2.7.3.jar
assembly/target/scala-2.11/jars/hadoop-hdfs-2.7.3.jar
assembly/target/scala-2.11/jars/hadoop-mapreduce-client-app-2.7
```
Like I've said before, that's a bit dangerous, especially with a
hadoop-cloud-projects POM module now upstream. We won't ever produce a
hadoop-cloud-projects JAR, so there won't be direct conflict, more potential
confusion if people see a jar beginning hadoop-* with different version info.
---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org
