|Re: [jetty-users] Keep Jetty instance alive in daemon mode after maven command completes|
http://wiki.eclipse.org/Jetty/Feature/Jetty_Maven_Plugin#jetty:run-forked__:__Running_an_unassembled_webapp_in_a_separate_jvm Use <waitForChild>false</waitForChild> Jan On 26 October 2012 05:23, Fhomasp <thomas.peeters1@xxxxxxxxxx> wrote: > Yes, I'd like to keep Jetty alive after the build has finished. Otherwise I > guess I wouldn't have bothered posting :-) > > The idea is that we initiate some kind of nightly build which allows our > testers to immediately access the newest snapshot version when they arrive > in the morning. Given that the build succeeds of course. > > > > -- > View this message in context: http://jetty.4.n6.nabble.com/Keep-Jetty-instance-alive-in-daemon-mode-after-maven-command-completes-tp4959365p4959396.html > Sent from the Jetty User mailing list archive at Nabble.com. > _______________________________________________ > jetty-users mailing list > jetty-users@xxxxxxxxxxx > https://dev.eclipse.org/mailman/listinfo/jetty-users -- Jan Bartel <janb@xxxxxxxxxxx> www.webtide.com – Developer advice, services and support from the Jetty & CometD experts.
Back to the top