Errors when deploying to Heroku

[jaybytez]

Thank you for the tutorial, this is exceptionally helpful.

I can easily get Play to run on AWS, but I have been unsuccessfully able to deploy on Heroku. I created an account and then followed the steps listed in this tutorial.

If I follow the steps of creating the play2torial and even stop and the base application before doing all the configuration of views (meaning the standard app template), the application produces an error when I run heroku open (after following the deployment steps and creating the Procfile): 2015-03-04T20:33:24.826458+00:00 app[web.1]: bash: target/start: No such file or directory
2015-03-04T20:33:25.639509+00:00 heroku[web.1]: Process exited with status 127.

So since that didn't work for me, I tried to follow the cheat section where I just follow your instructions from (git clone git://github.com/jamesward/play2torial.git) and I receive the following error going that path:

remote: [info] Compiling 1 Scala source to /tmp/scala_buildpack_build_dir/.sbt_home/plugins/target/scal
a-2.9.1/sbt-0.11.3/classes...
remote: [error] error while loading CharSequence, class file '/tmp/scala_buildpack_build_dir/.jdk/jre/l
ib/rt.jar(java/lang/CharSequence.class)' is broken
remote: [error](bad constant pool tag 18 at byte 10)
remote: [error] one error found
remote: [error] {file:/tmp/scala_buildpack_build_dir/.sbt_home/plugins/}default-847120/compile:compile:
Compilation failed
remote: Project loading failed: (r)etry, (q)uit, (l)ast, or (i)gnore?
remote: ! ERROR: Failed to run sbt task: update
remote:
remote:
remote: ! Push rejected, failed to compile Play 2.x - Java app
remote:
remote: Verifying deploy...
remote:
remote: ! Push rejected to shielded-beach-5570.
remote:
To https://git.heroku.com/shielded-beach-5570.git
! [remote rejected] origin/java-heroku_update -> master (pre-receive hook declined)
error: failed to push some refs to 'https://git.heroku.com/shielded-beach-5570.git'

Of course, after the git, only the two *.md files are pulled down.

Deploying the project using the new sbt-heroku plugin does work (https://www.playframework.com/documentation/2.3.x/ProductionHeroku), however the view looks different from the my local instance as the remote only shows the message "Your new application is ready.". But this looks more like something related to the dist mode because when I run the start bat in the universal directory, it's not able to iframe in the remainder of the getting started content.

Sorry for such a noob question...thanks for the pointers.

[jaybytez]

I changed the Procfile to this and it worked with the git deployment:

web: target/universal/stage/bin/play2torial -Dhttp.port=${PORT}

This post spoke to an issue with the JAVA_OPTS - http://stackoverflow.com/questions/19391014/play-2-2-application-crashes-on-heroku

[jamesward]

What version of Play are you using? It looks like an older one. Your original push error was due to using a version of Scala that isn't compatible with Java 8.

[jaybytez]

Thanks for responding so quickly and sorry for not including the versions.

I am running the latest version of the activator: activator-1.3.2-minimal

And my other properties from build.sbt and plugins.sbt:

scalaVersion := "2.11.1"
addSbtPlugin("com.typesafe.play" % "sbt-plugin" % "2.3.8")

My local version of Java is: java version "1.7.0_55"

[jamesward]

What about the sbt version? (From project/build.properties)

[jaybytez]

It's set to sbt.version=0.13.5 and I have the latest activator which appears to be running 0.13.7

[jamesward]

The error above indicates sbt-0.11.3 so I'm not sure what could be causing a different version of sbt to be used.

[okahara]

I have the same error and i am using sbt.version=0.11.3

any solution? suggestion?

[jamesward]

I've totally reworked this tutorial for Play 2.3. Here is the diff:
cc2117c#diff-51809c480fa821da30c46a075e0b672b

Hopefully that will help those of you having issues here.