Debugging Lift apps with ensime, jdb, jetty, sbt

[Sahale]

I am migrating from IntelliJ to Ensime, and have been very happy to
date to be back in emacs land with a powerful and very responsive text
editor, now endowed with modern ide-like smarts around scala.

However, after going through the ensime docs, and spending a while
fruitlessly searching this group and googling the web, I am puzzled as
to how to configure things to debug my lift jetty-based app. I have
tried modifying my sbt launcher so that it is waiting for a remote
socket attach, e.g.:

java -Dsbt.boot.properties="sbt.boot.properties" -Xdebug -
Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=5005
-XXCMSClassUnloadingEnabled -XX:MaxPerm Size=256m -Xmx1024m -Xss4m -
jar `dirname $0`/sbt-launch.jar "$@"

...and then passing -attach localhost:5005 to ensime's jdb VM
parameters, but ensime's debugger code still wants to run a new VM for
the jdb session. Are others just launching jetty inside of the ensime
jdb process rather than attaching to one spawned by sbt? Is it a bad
assumption to think the ensime debugger configuration allows attaching
to a remote java process? What do people's workflow look like for
debugging with ensime and lift?

Thanks in advance,

-JW

[Guillaume Massé]

Bump.

work great on emacs

https://github.com/aemoncannon/ensime/issues/244

currently working on it for sublime-ensime :-)

Guillaume