There are two possible solutions I have found:
In the Jetty launcher you set the context to go directly to the war file generated by staging using
context.setWar("target/scala-2.10/mywar_2.10-0.0.1.war")
. In this case you still run with embedded Jetty and the StartScriptPlugin.startScriptForClassesSettings key, but it runs from the WAR instead ofUse Heroku's deploy:war capability: https://devcenter.heroku.com/articles/war-deployment . This didn't work well for me because it means everything is now running in an environment I don't really understand and Heroku is shy on supporting this.