Attempt with extra repositories
Remove trailing slashes from repository specifications.

The correct format is to not have a trailing slash.

For me this caused non-deterministic failures due to issues fetching
certain artifacts. The issue was that some of the maven caches would
fail to fetch the artifact (due to the way that the artifact
path was concatenated with the repository) and this short-circuited
the download process in a silent way. Here is what the log output
looked like:

    Downloading: http://repo.maven.apache.org/maven2/org/spark-project/akka/akka-remote_2.10/2.2.3-shaded-protobuf/akka-remote_2.10-2.2.3-shaded-protobuf.pom
    [WARNING] The POM for org.spark-project.akka:akka-remote_2.10:jar:2.2.3-shaded-protobuf is missing, no dependency information available

This was pretty brutal to debug since there was no error message
anywhere and the path *looks* correct as reported by the Maven log.
Removing extra code in new yarn
Cleanup
Clean-up
One other fix
Merge pull request #268 from pwendell/shaded-protobuf

Add support for 2.2. to master (via shaded jars)

This patch does a few related things. NOTE: This may not compile correctly for ~24 hours until artifacts fully propagate to Maven Central.

1. Uses shaded versions of akka/protobuf. For more information on how these versions were prepared, see [1].

2. Brings the `new-yarn` project up-to-date with the changes for Akka 2.2.3.

3. Some clean-up of the build now that we don't have to switch akka groups for different YARN versions.

[1]
https://github.com/pwendell/spark-utils/tree/933a309ef85c22643e8e4b5e365652101c4e95de/shaded-protobuf
spark-898, changes according to review comments
spark-968, changes for avoid a NPE
Update Svdpp.scala
Test SVD++
Update Svdpp.scala
Update AnalyticsSuite.scala
Merge pull request #102 from ankurdave/clustered-edge-index

Add clustered index on edges by source vertex
Update Svdpp.scala
Update Svdpp.scala
Update Svdpp.scala
Fixed a performance problem in RDD.top and BoundedPriorityQueue (size in BoundedPriority was actually traversing the entire queue to calculate the size, resulting in bad performance in insertion).
Fixed the example link.
objectSer -> valueSer in a test.