This actually fits with some things I'd been thinking about - namely, the
ability to turn off the auto-archiving of artifacts/javadoc/static
analysis/coverage/etc for a project. For example, I've got a project which, in
its nightly build, generates javadoc and then zips it up with an assembly. But
Hudson (specifically the Maven plugin) sees the javadoc mojo fire, and
automatically archives the Javadoc, whether I want it to do so or not. Or I'm
running Cobertura in the project, but I don't have the Cobertura plugin enabled
for the project in Hudson - and yet it still archives the Cobertura reports,
because the mojo fired.
I'm not sure if there's an elegant way to handle this, and it's probably not
worth doing anything about unless there's an elegant way to handle it. But
it's something to consider.
fix the summary.