Note that there are some explanatory texts on larger screens.

plurals
  1. POWhy doesn't SBT 0.7.7 work correctly on my Linux system? (case details inside)
    text
    copied!<p><em>First of all, I'd like to ask to correct my question title if something better comes into your mind.</em></p> <p>Let's take a Lift REST web service example from the Simply Lift book by David Pollak <a href="https://github.com/dpp/simply_lift/tree/master/samples/http_rest" rel="nofollow">here</a>.</p> <p>If I open a Windows (Windows XP SP3, all the updates, Oracle JDK 7) console inside the directory and run "sbt" (sbt.bat), everything works just fine. But in case I try to do the same (but using "./sbt") in Linux (XUbuntu 11.10, OpenJDK 6, OpenJDK 7, Oracle JDK 7 (tried all of them)), SBT returns (instead of going to SBT console mode) immediately as it has done it's job. This means that may the command be just <code>./sbt</code> it returns about immediately (after finishing the automatic project maintenance), or be it <code>./sbt jetty-run</code> - it just starts the web server and <em>shuts it down immediately</em>.</p> <p>Moreover, a web service I've developed for a project of mine compiles and works ok on Windows, but can't be compiled (using <code>./sbt compile</code>) on Linux (by the same version of SBT). The error is "source file '/.../src/main/scala/code/lib/FooBar.scala;src/main/scala/bootstrap/liftweb/Boot.scala' could not be found", where "FooBar.scala" is an object where I do all the serves (directly called from Boot.scala).</p> <p>Any ideas of what can be the reason and how to fix it?</p> <p><b>UPDATE:</b> The reason of the first problem (SBT returning to shell instead of offering SBT console) seems to be the file was checked out on Windows and had CR+LF instead of just LF line ending. The solution of source files not being found was in just using <code>clean</code> command to recompile from scratch.</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload