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 incremental builds turned on and SCM polling. Normally this works just fine. Every now and then, though, that root pom project shows up in the "-pl" argument to Maven, when that root pom.xml does not show up in the list of files changed. Is this a known issue? Am I doing something wrong? Best, Laird -- http://about.me/lairdnelson
