GitHub user srowen opened a pull request:
https://github.com/apache/spark/pull/145
SPARK-1254. Consolidate, order, and harmonize repository declarations in
Maven/SBT builds
This suggestion addresses a few minor suboptimalities with how repositories
are handled.
1) Use HTTPS consistently to access repos, instead of HTTP
2) Consolidate repository declarations in the parent POM file, in the case
of the Maven build, so that their ordering can be controlled to put the fully
optional Cloudera repo at the end, after required repos. (This was prompted by
the untimely failure of the Cloudera repo this week, which made the Spark build
fail. #2 would have prevented that.)
3) Update SBT build to match Maven build in this regard
4) Update SBT build to not refer to Sonatype snapshot repos. This wasn't in
Maven, and a build generally would not refer to external snapshots, but I'm not
100% sure on this one.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/srowen/spark SPARK-1254
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/spark/pull/145.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 #145
----
commit 42f9bfc1786f2b9b594adbbce09d4b22a77d5e68
Author: Sean Owen <so...@cloudera.com>
Date: 2014-03-14T21:34:36Z
Use HTTPS for repos; consolidate repos in parent in order to put optional
Cloudera repo last; harmonize SBT build repos with Maven; remove snapshot repos
from SBT build which weren't in Maven
----
---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
