As a result of changes in 664f2cc the start command contains hard-coded references to the staging directory. For example, deploying java-main from https://github.com/cloudfoundry/java-test-applications results in a startup file with the following contents:

...
(/tmp/staged/app/.java/bin/java -cp . -Dalpha=bravo -Xss1M com.gopivotal.test.JavaMain) > $DROPLET_BASE_DIR/logs/stdout.log 2> $DROPLET_BASE_DIR/logs/stderr.log &
...

Similarly, deploying web-application results in the following:

...
(JAVA_HOME=/tmp/staged/app/.java JAVA_OPTS="-Dhttp.port=$PORT -Xss1M" /tmp/staged/app/.tomcat/bin/catalina.sh run) > $DROPLET_BASE_DIR/logs/stdout.log 2> $DROPLET_BASE_DIR/logs/stderr.log &
...

Consequently, deployment fails with an error such as ./startup: line 18: /tmp/staged/app/.java/bin/java: No such file or directory.