[
https://issues.apache.org/jira/browse/SPARK-6182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Patrick Wendell resolved SPARK-6182.
------------------------------------
Resolution: Fixed
Fix Version/s: 1.3.0
Assignee: Sean Owen
> spark-parent pom needs to be published for both 2.10 and 2.11
> -------------------------------------------------------------
>
> Key: SPARK-6182
> URL: https://issues.apache.org/jira/browse/SPARK-6182
> Project: Spark
> Issue Type: Bug
> Components: Build
> Affects Versions: 1.3.0
> Reporter: Patrick Wendell
> Assignee: Sean Owen
> Priority: Blocker
> Fix For: 1.3.0
>
>
> 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).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
