No it doesn't work for sitemap... as thats loaded at boot only ;-) My point was that it can still be a good experience without JR for our users.
Interesting what you were saying about your dev style... i'm usually the other way around and implement sitemap last as I see it as a concrete setting of my content. Cheers, Tim On 9 Mar 2010, at 11:20, Jeppe Nejsum Madsen wrote: > On Tue, Mar 9, 2010 at 12:08 PM, Timothy Perrett > <[email protected]> wrote: >> 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 :-) > > But still this doesn't address the problem (I think?) of changing > things in Boot. Maybe I code differently from everybody else, but when > iterating new features, I always end up making lots of changes to > Sitemap. And afaik everyone of those changes requires a restart.... > > For the rest I agree JRebel fits quite nicely (it does have it's > problems as David points out) > > /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.
