When a maven2 job is configured to clean up old builds, it does so only for the parent and not for the
modules. Possibly there is a work around when you explicitly configure cleaning for every module, but that
would mean that hudson is not fire-and-forget when adding new maven2 subprojects.