JRebel and sbt do very different things.
Sbt is an alternative to maven. It's a build tool. You can get continuous
compilation with maven by typing mvn scala:cc. Sbt currently has better
dependency analysis, to know when to recompile what. Maven currently has two
modes: -Drecompilation-mode=modi
I'm new to maven so I just followed the Lift Getting Started
guide, which uses "mvn jetty:run" to start jetty and ctrl-c to stop it.
I used sbt before for another project that uses a different framework
and like it that it auto-compiles the changed files and restarts jetty
(as far as I remember -
How do you launch jetty? If it's an eclipse maven launch, specify JRebel in the
JVM arguments. For command-line maven, specify it in the MAVEN_OPTS environment
variable.
If you launch via sbt (assuming there's such a thing) then you have to check
the sbt docs.
Ultimately the command line that la
Thanks.
"The Eclipse incremental compiler, Jetty & the JRebel plugin makes for
fairly rapid turnaround times."
This is interesting. I wonder if there are instructions somewhere online
about how to use Eclipse + sbt + JRebel for Lift development. The Lift
Get Started Guide mentions a lot of start
Hi,
A while ago, I started writing an experience report on using Scala &
Lift. I finally finished this (it has been a little more than 6 months
now, time is flying :-)
http://jeppenejsum.wordpress.com/2010/01/18/scala-and-lift-status-after-six-months/
/Jeppe
--
You received this message because
