When adding the sbt-start plugin to push to Heroku, via build.sbt with the following contents:
resolvers += Classpaths.typesafeResolver
addSbtPlugin("com.typesafe.startscript" % "xsbt-start-script-plugin" % "0.5.3")
I get an unresolved dependency with play:
[warn] module not found: play#sbt-plugin;2.0.4
[warn] ==== local: tried
[warn] /Users/david-grandes/.ivy2/local/play/sbt-plugin/scala_2.9.2/sbt_0.12/2.0.4/ivys/ivy.xml
[warn] ==== typesafe-ivy-releases: tried
[warn] http://repo.typesafe.com/typesafe/ivy-releases/play/sbt-plugin/scala_2.9.2/sbt_0.12/2.0.4/ivys/ivy.xml
[warn] ==== Typesafe repository: tried
[warn] http://repo.typesafe.com/typesafe/releases/play/sbt-plugin_2.9.2_0.12/2.0.4/sbt-plugin-2.0.4.pom
[warn] ==== public: tried
[warn] http://repo1.maven.org/maven2/play/sbt-plugin_2.9.2_0.12/2.0.4/sbt-plugin-2.0.4.pom
[warn] ::::::::::::::::::::::::::::::::::::::::::::::
[warn] :: UNRESOLVED DEPENDENCIES ::
[warn] ::::::::::::::::::::::::::::::::::::::::::::::
[warn] :: play#sbt-plugin;2.0.4: not found
[warn] ::::::::::::::::::::::::::::::::::::::::::::::
Which is weird considering that if we remove the sbt-start-plugin, we can actually find the play plugin with no problems.
EDIT
Maybe its related to this specific version of the plugin? https://github.com/sbt/sbt-start-script/issues/23