Hello; thanks for a great product. I am using my h2-maven-plugin (http://github.com/ljnelson/h2-maven-plugin) project to spawn long-lived H2 server processes. Doing this from the command line works great: after I run mvn com.edugility:h2-maven-plugin:1.0:spawn, I get a new H2 server listening on port 9092.
The internals of the Maven plugin effectively launch a new JVM by using ProcessBuilder and Process#start(). When I bake this invocation into a Jenkins build, the process is terminated as soon as the build completes. That's not what I want. My (Jenkins) question is: does Jenkins--when spawning Maven--do something explicit to kill the entire process tree when it is completed? Because in my case, I want my long-lived H2 process to continue after the Maven JVM that invoked it is killed. I freely recognize this may just be one of those cases where it's Just Not Going To Work but I thought I'd ask to see if Jenkins is doing anything specific to kill the entire tree of processes that might have been spawned as a result of a Maven job. Thanks, Laird -- http://about.me/lairdnelson
