Blocker Description
A recent bug report (SPARK-5143) pointed out that the parent pom had the wrong scala version property when building for Scala 2.11. The fix for that issue correctly sets the parent pom property when the manual bash script is invoked to update Spark to scala 2.11.
For published artifacts, however, an issue still remains. Because our parent pom does not have a scala identifier, we can't publish two of them for scala 2.10 and 2.11. The fix is simple, we just need to add a scala version identifier to the parent pom and update all references to that parent.
For more details on how our current publishing process works, see this script:
https://github.com/apache/spark/blob/master/dev/create-release/create-release.sh#L119
We do a mvn install under both builds, then we manually copy the artifacts to the ASF nexus repository (necessary because Maven does not support cross-publishing nicely).
