You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Josh Rosen (JIRA)" <ji...@apache.org> on 2016/06/09 18:14:20 UTC
[jira] [Resolved] (SPARK-15827) Publish Spark's forked
sbt-pom-reader to Maven Central
[ https://issues.apache.org/jira/browse/SPARK-15827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Josh Rosen resolved SPARK-15827.
--------------------------------
Resolution: Fixed
Fix Version/s: 2.0.0
1.6.2
Fixed by my patch for master, 2.0.0, and 1.6.2.
> Publish Spark's forked sbt-pom-reader to Maven Central
> ------------------------------------------------------
>
> Key: SPARK-15827
> URL: https://issues.apache.org/jira/browse/SPARK-15827
> Project: Spark
> Issue Type: Improvement
> Components: Build, Project Infra
> Reporter: Josh Rosen
> Assignee: Josh Rosen
> Fix For: 1.6.2, 2.0.0
>
>
> Spark's SBT build currently uses a fork of the sbt-pom-reader plugin but depends on that fork via a SBT subproject which is cloned from https://github.com/scrapcodes/sbt-pom-reader/tree/ignore_artifact_id. This unnecessarily slows down the initial build on fresh machines and is also risky because it risks a build breakage in case that GitHub repository ever changes or is deleted.
> In order to address these issues, I propose to publish a pre-built binary of our forked sbt-pom-reader plugin to Maven Central under the org.spark-project namespace.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org