Heroku添加sbt start插件可防止sbt插件解析

Question

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

Answer 1

It is odd that removing the sbt-start-plugin allows play#sbt-plugin;2.0.4 to be found because I believe that play#sbt-plugin;2.0.4 is only available for Scala 2.9.1 and SBT 0.11.3 . Perhaps when you added sbt-start-plugin you also changed the Scala or SBT version?

Nonetheless, unlike deploying other Scala web frameworks to Heroku, the sbt-start-plugin should not be necessary to deploy a Play 2.0 application to Heroku because Play 2.0 already includes the required stage task so deployment to Heroku should work out of the box. If you take a fresh Play 2.0 app, you can deploy it to Heroku without any modifications.