This breaks generation of site when wagon-scm is in the build extensions, eg. to deploy the site to svn or cvs for Collabnet (dev.java.net)

When running site Maven tries always to instantiate projec-info-report mojos before checking in the pom for "exclude default reports" option.

The only way to generate the site was install the project-info-report plugin after removing the class ScmReport. It has to go under the same groupId, org.apache.maven.plugins, which makes it a real hack

This would require some heavy refactoring to introduce a new way to manage artifacts in the core classloader during the resolution process. See MNG-2225 for more information.

Another worst problem is that it causes the release:prepare to fail too

New patch with less snapshots

this caused some problems with the release plugin because jdom was in the root container (via wagon-webdav), but jaxen was not (because it is optional, so it was not caught by the resolution I added).

I have an alternate solution putting extensions in a child container like plugins which is working. I will clean up and commit tomorrow.

This could be reviewed and handled differently for trunk given the changes to plexus and classworlds. I'll examine that separately.