Because xsbt-web-plugin does not fork a Java process when you run container:start
, there's no way to use sbt's javaOptions
to do this. Instead, you'll have to instrument the sbt process itself to see any JMX info.
To do this, add the following line to your ~/.sbtconfig file:
SBT_OPTS="$SBT_OPTS -Dcom.sun.management.jmxremote -Dcom.sun.management.jmxremote.ssl=false -Dcom.sun.management.jmxremote.authenticate=false -Dcom.sun.management.jmxremote.port=1099"