GitHub user JoshRosen opened a pull request:
https://github.com/apache/spark/pull/13564
[SPARK-15827][BUILD] Publish Spark's forked sbt-pom-reader to Maven Central
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.
For now, I've staged a release of the plugin at
https://oss.sonatype.org/content/repositories/orgspark-project-1124 and have
reconfigured the build to use that. This release was built from
https://github.com/JoshRosen/sbt-pom-reader/tree/v1.0.0-spark, which contains
the contents of @ScrapCodes's branch plus an additional patch to configure the
build for artifact publication.
Provided that all of the tests pass and the artifacts look okay, I plan to
promote the release to Maven Central and rebase.
/cc @srowen @ScrapCodes for review.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/JoshRosen/spark
use-published-fork-of-pom-reader
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/spark/pull/13564.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #13564
----
commit d4078463d1937217d2b167c1cd370074efb62d8d
Author: Josh Rosen <[email protected]>
Date: 2016-06-08T18:58:56Z
Add staging repository for forked POM reader.
----
---
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]
