Github user srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/2318#discussion_r17232323
--- Diff: assembly/pom.xml ---
@@ -26,7 +26,7 @@
</parent>
<groupId>org.apache.spark</groupId>
- <artifactId>spark-assembly_2.10</artifactId>
+ <artifactId>spark-assembly</artifactId>
--- End diff --
It goes without saying, but this introduces a sort of 'incompatibility' at
the Maven level. Downstream projects have to change artifact _and_ version when
selecting between this and a future version with different artifact names. This
doesn't automatically harmonize the Spark build with the version of Scala
you're using, and Maven can't resolve dependency conflicts across differently
named artifacts. These are kind of inevitable.
If an end goal is to publicly support Scala 2.10 and 2.11 simultaneously,
then we still have to have several published artifacts at once right? this is
what `classifier` could be used for. But I suppose it's worth asking if that's
the intent? or is this going to may be happen all at once for Spark 2.x?
---
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]
