This can only be implemented in the corresponding reports, eg the pmd plugin has a maven.pmd.failonerror property, checkstyle has maven.checkstyle.fail.on.violation, etc.

I was thinking more along the lines of using the jelly:catch tag, and swallowing the BuildException (or whatever gets thrown).

Patch to ignore report failures.

Provide a better message.

Can you provide a patch for the docs as well?
What will happen if you set eg maven.checkstyle.fail.on.violation=true but maven.site.reports.failonerror=false?

Patch including xdocs.

>> What will happen if you set eg maven.checkstyle.fail.on.violation=true but maven.site.reports.failonerror=false?

Haven't tried, but the checkstyle report will fail, but the site generation should continue. (The checkstyle report should become a broken link.)

The Use Case for this issue is when I don't need all of the reports to succeed before the site gets generated/deployed. For example, even if the source violated checkstyle, I still want to see my javadoc. As you commented earlier, not all plugins support don't-fail-on-error options.

Patch applied with slight modifications. I renamed the property to maven.site.reports.ignoreErrors which appeared more logical
(eg the build did not fail with maven.checkstyle.fail.on.violation=false but maven.site.reports.failonerror=true). Thanks!