BTW, with SBT, don't forget you can do:
jetty-run
(make changes to your code)
prepare-webapp
That will redeploy chnaged files / classses to the running jetty
instance so development with SBT can still be slick without
javarebel :-)
Lift is really elegant - some how, this approach feels pretty ugly. I
haven't looked at it, but no doubt it's using some classloader trickery?
Cheers, Tim
Sent from my iPhone
On 9 Mar 2010, at 10:45, Lukasz Kuczera <[email protected]> wrote:
But on the other hand it happens not too often. I'm personally very
very happy with current productiveness using Lift + Jetty + JRebel.
But what happens when Zeroturnaround will turn back to Scala ? It is
quite possible that Scala will go mainstream. It might be viable
solution then.
Simple solution would be putting Menu building just before page
rendering in "development" mode. But i can live perfectly without that
as well (using JRebel).
On Mar 9, 9:37 am, Jeppe Nejsum Madsen <[email protected]> wrote:
On Tue, Mar 9, 2010 at 9:33 AM, Timothy Perrett
<[email protected]> wrote:
I'm afraid I agree with Marius... I'm just not sure on the benefit
here over
JRebel?
My main pain point was changes to Sitemap. JRebel doesn't help you
here as it's fixed once Lift is booted...
/Jeppe
--
You received this message because you are subscribed to the Google
Groups "Lift" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to [email protected]
.
For more options, visit this group at http://groups.google.com/group/liftweb?hl=en
.
--
You received this message because you are subscribed to the Google Groups
"Lift" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/liftweb?hl=en.
