Basically, add an action to SBT that will bundle the war and Jetty into one executable, big, fat, jar.
I'll try a backport to 6.x and see how that goes.... (with Comet)
Alternatives have evolved since. Please re-open if you have specific needs :)
Basucally, you mean the work that I did. That still broke the jetty continuations detection (I thin I saw it breaking in another place as well....). See the Google thread in this link.
a) the Jetty continuations break thing needs to be fixed
b) If that has been done and what Glen and I did is the solution, we need to document that
c) if there is another solution which one
Imported from Assembla: http://www.assembla.com/spaces/liftweb/tickets/909
It sounds like it's easier these days to bundle jetty into the system. I think @farmdawgnation has done it? Assuming that's true, Farmer, is it reasonable to roll this into Lift, or should it be external?
Yeah, I do this regularly. This should be rolled into an sbt plugin, not a feature in the framework. Closing this ticket accordingly.
Until we get that sbt plugin, and for reference, this project uses the assembly sbt plugin to bundle jetty and all you need to run your lift app into a single jar https://github.com/fmpwizard/lift_starter_2.4/tree/raspberrypi-gpio
Perfect, thanks for adding that here :)