No sbt REPL

[tigerfoot]

Hello,

I just downloaded sbt on my mac and now I don't get a REPL console if I just run sbt.  I can run commands like "sbt clean" and they work fine.

My launch script is:

java -Xms512M -Xmx1536M -Xss1M -XX:+CMSClassUnloadingEnabled -XX:MaxPermSize=384M -jar /usr/local/libsbt-launch.jar "$@"

Any ideas why no REPL?

Thanks,

Greg

[Mark Harrah]

What do you mean by "no REPL"? If you run $sbt, it exits immediately without any message?

-Mark

> Thanks,
> Greg
>
> --
> You received this message because you are subscribed to the Google Groups "simple-build-tool" group.
> To view this discussion on the web visit https://groups.google.com/d/msg/simple-build-tool/-/TPC4CR3WnwcJ.
> To post to this group, send email to simple-b...@googlegroups.com.
> To unsubscribe from this group, send email to simple-build-t...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/simple-build-tool?hl=en.
>

[tigerfoot]

Yes, exactly.  Before I could just run sbt and get a prompt where I can run sbt commands.  Now I just exit to the os.

[Harald Meland]

On Tue, Aug 21, 2012 at 1:39 AM, tigerfoot <gzo...@gmail.com> wrote:
> Yes, exactly. Before I could just run sbt and get a prompt where I can run
> sbt commands. Now I just exit to the os.

If this really is your launch script:

>> > java -Xms512M -Xmx1536M -Xss1M -XX:+CMSClassUnloadingEnabled
>> > -XX:MaxPermSize=384M -jar /usr/local/libsbt-launch.jar "$@"

then I'd double-verify that the referred jar file really is present:

ls -l /usr/local/libsbt-launch.jar

I suspect there might be a typo in there, and the path should really
be /usr/local/lib/sbt-launch.jar (with an extra slash after "lib").
--
Harald

[tigerfoot]

There was a typo, but in my post, not in the actual script.

But... the truth is even stranger.  If I enter the contents of the sbt script directly to the OS command prompt: java -Xms.....
everything works fine.  But if I run the script, containing the exact same command, I get dumped to the OS.

Upon closer inspection the script had an '@' sign by its permissions.  Not sure what that means, but when I created a new text file, copied the command into it, and chmod a+x, then it was happy.  Whatever '@' means it was messing it up.

-gz

[Harald Meland]

On Tue, Aug 21, 2012 at 11:29 PM, tigerfoot <gzo...@gmail.com> wrote:
> Upon closer inspection the script had an '@' sign by its permissions. Not
> sure what that means,

Googling "unix file permissions at sign" brought me to:
http://blog.anselmbradford.com/2008/12/24/what-is-the-significance-of-plus-and-at-in-mac-os-x-file-permission-tables/
... which seems like a likely cause for the troubles you've experienced.
--
Harald