Github user JoshRosen commented on a diff in the pull request:
https://github.com/apache/spark/pull/12334#discussion_r59598076
--- Diff: assembly/pom.xml ---
@@ -20,7 +20,7 @@
<modelVersion>4.0.0</modelVersion>
<parent>
<groupId>org.apache.spark</groupId>
- <artifactId>spark-parent_2.11</artifactId>
+ <artifactId>spark-parent</artifactId>
--- End diff --
Empirically, it looks like the generated POMS which are used for publishing
end up with all variables in the `<dependencies>` section having been expanded
according to whichever profile was active at publication time. For example, in
http://central.maven.org/maven2/org/apache/spark/spark-core_2.10/1.6.1/spark-core_2.10-1.6.1.pom,
there are no references to `scala.binary.version` in the `<dependencies>`
section. There _are_ references in the `<build>` section but I don't think that
this is relevant to consumers of this POM since I don't expect people to depend
on our child POMs in their own builds.
---
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]
