We are in the process of upgrading our build processes and infrastructure. The majority of the projects are still stuck using Maven 2.2.1 (we have hundreds of Maven projects across a number of environment on different Hudson and Jenkins servers). An immediate upgrade to 3.3.x will most-certainly break things for us due to the number of teams affected and large amount of projects which haven't been looked after, or have become obsolete.
As part of the migration, we would temporarily like to disable the generation and deployment of Maven sites. In the more recent versions of the maven-site-plugin there is there are two properties that would have come quite handy - maven.site.skip and maven.site.deploy.skip, however we are unfortunately stuck Maven 2.2.1 where these versions are completely ignored.
Is there another way to disable this?
There probably is no "clean" way to do this but some possibilities exist:
If you don't add a site section inside <distributionManagement/> the site will not be uploaded. See: http://maven.apache.org/pom.html#Site_Distribution
So remove that section from the pom might help in your situation.
Another try would be to deploy the site to /tmp/maven-sites by specifying file:///tmp/maven-sites for the site deployment url. Unfortunately, deploying to file:///dev/null would not work, as the maven-site-plugin would need to be able to create files and directories. :)