|Re: [jetty-users] Keep Jetty instance alive in daemon mode after maven command completes|
I saw that example, however it's no good to me. If I use that config and
don't provide a jetty:stop execution Jetty still stops running in Daemon
mode. When I do not use daemon mode the maven command keeps running
indefinately and never gives a "build success" message. I need that to
evaluate the CI build as successful.
So what I need is a maven command that starts Jetty, deploys my war or ear
file, and issues a build-success. After that Jetty needs to be running
until we issue a jetty:stop command, for example when the next build starts.
I hope I'm clear enough. Thanks already Jan
View this message in context: http://jetty.4.n6.nabble.com/Keep-Jetty-instance-alive-in-daemon-mode-after-maven-command-completes-tp4959365p4959385.html
Sent from the Jetty User mailing list archive at Nabble.com.
jetty-users mailing list
Back to the top