https://bugzilla.redhat.com/show_bug.cgi?id=1112196
Olivier Samyn code@oleastre.be changed:
What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(code@oleastre.be) |
--- Comment #2 from Olivier Samyn code@oleastre.be --- Thanks for your quick answer. I mainly develop Play based web applications that sometimes uses quite complex build involving sub-modules and external dependencies.
The problem I faced that triggered this bug report is that I had to run my application in debug mode without a way to specify that on the sbt command line.
Aside of that, there is another bug #1083130 that asks to be able to specify memory options. This is a second canditate.
So, here is a small "wishlist" from the help options of upstream scripts:
-d | -debug set sbt log level to debug -no-colors disable ANSI color codes -sbt-dir <path> path to global settings/plugins directory (default: ~/.sbt) -sbt-boot <path> path to shared boot directory (default: ~/.sbt/boot in 0.11 series) -ivy <path> path to local Ivy repository (default: ~/.ivy2) -mem <integer> set memory options (default: 1536, which is -Xms1536m -Xmx1536m -XX:MaxPermSize=384m -XX:ReservedCodeCacheSize=192m) -jvm-debug <port> Turn on JVM debugging, open at the given port. -java-home <path> alternate JAVA_HOME
Aside of that, the script should also support environment variables: JAVA_OPTS and SBT_OPTS and passing variables to the java runtime (-Dkey=val and -J-X)