On my hudson server I have a maven job for all Hudson plugins because
Im too lazy to create separate jobs for each plugin and I dont really
see an advantage of doing that. The downside for this is that I use
SCM Polling for job which trigger a rebuild of all modules, even if it
is only one module that has changed. A full rebuild takes longer and
longer, as more and more plugins are added.

Ive been thinking if it would be possible to do a little smarter
rebuild for maven jobs with modules. What if the maven job could use
the file paths from the
build.getChangeSet().getItems().getAffectedPaths() method, and only
call the maven goals for those paths? It should somehow find the
deepest pom.xml and use that for each path. I guess if there are
dependencies within the modules, that should be solved as well.