I'm seeing occasional cases where a change to a single .java file in a
single Maven module is causing Jenkins to believe that it needs to rebuild
the entire world (well, rather, it is detecting incorrectly that the root
pom.xml has changed, thus causing a rebuild of the world).
I obviously have in
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
