Github user vanzin commented on the pull request:
https://github.com/apache/spark/pull/4913#issuecomment-77402903
With this change is `scala.binary.version` even needed anymore?
Also, how does it work in the end? It may work, but I see some weirdness
here. For example, you'll still be publishing a single spark-parent pom, right?
That pom still declares some dependencies with the now hardcoded `_2.10`
version, such as `com.twitter:chill`. If no one uses those directly things
should work, but it someone ends up using it, and they want Scala 2.11, they'll
probably get the wrong version, no?
---
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]
