Scala Application launcher will only work with main class within selected project, rather than those on classpath
The Scala Application launcher checks for the availability of the main class in the current project. This means it's not possible to launch using a main class available on the classpath. In this case, I wanted to launch sbt/Play to use the Scala debugger because there's not currently a remote launcher:
Cannot location main type 'xsbt.boot.Boot' in project 'test'. For this to work, the package name in the source needs to match the source's physical location. hint: Move the source file containing the main type 'xsbt.boot.Boot' in folder 'xsbt/boot'.
The Java Application launcher permits this and can be used as a workaround, as long as the Scala Debugger isn't needed.
Cannot location main type 'xsbt.boot.Boot' in project 'test'. For this to work, the package name in the source needs to match the source's physical location. hint: Move the source file containing the main type 'xsbt.boot.Boot' in folder 'xsbt/boot'.
The Java Application launcher permits this and can be used as a workaround, as long as the Scala Debugger isn't needed.
Leave a comment
on 2012-10-11 03:23 *
By Iulian Dragos
Component changed from Eclipse to Debugger
Milestone set to To Discuss
on 2012-11-08 04:53 *
By Iulian Dragos
I can't reproduce this using the description in the title: I have a small jar having a main class on the classpath of my project. I can create a Run configuration with that main class, and it runs fine.
It works for me using `sbt-launch.jar` and `xsbt.boot.Boot`. Closing this as Invalid, please reopen with more details if you still see this problem with a recent nightly build.