heroku/s3pository — pull request #4 by ryanbrainard (2012-05-22 04:16:18+00:00)
Title: Re-add /maven-scala-tools-releases pointing to oss.sonatype.org

Support for scala-tools in s3pository was dropped because of the repo sunsetting, but there are still artifacts that are only in scala-tools and not in Maven Central. This causes artifacts that can be resolved with a local, vanilla SBT to fail on pushes to Heroku. Instead of dropping all together, we should have pointed /maven-scala-tools-releases to https://oss.sonatype.org/content/groups/scala-tools/, per the note on http://scala-tools.org/.

We should also point /maven-scala-tools-snapshots to https://oss.sonatype.org/content/repositories/snapshots/ per the note, but holding off because it is already present under /maven-sonatype-oss, but only for .include("/com/force").include("/com/heroku"), so want to check if there is a reason for that.

Tested this with my staging s3pository using this buildpack:
BUILDPACK_URL=git://github.com/ryanbrainard/heroku-buildpack-scala.git#sbt-tools-sonatype-brainard