Checkstyle Plugin 2.8+ generates an additional aggregate report

Sebb,

This issue was cloned from MCHECKSTYLE-167, which was fixed in 2.9. That issue was that the numbers in the report was wrong. I think your issue is that the aggregate report is enabled by default, which is a change compared to previous versions. Is that the case?

Yes.

The original report that triggered the JIRA is here:
http://www.mailinglistarchive.com/html/users@maven.apache.org/2011-12/thrd4.html#00134

AIUI, the OP was complaining about two issues:

• 2.8 now generates an additional aggregate report
• the aggregate report has incorrect counts

2.9 fixes the incorrect count problem, but not the additional aggregate report.

Unfortunately, the JIRA settings at Codehaus are such that I could not re-open the original JIRA so I had to clone it.
[I intended to add some further explanation, but obviously forgot, sorry.]

It does not seem right that since 2.8 every Maven project now gets an additional aggregate report, regardless of whether the project actually has any modules to aggregate.

Work-round (see [1]):

  <reporting>
    <plugins>
.....
          <plugin>
            <groupId>org.apache.maven.plugins</groupId>
            <artifactId>maven-checkstyle-plugin</artifactId>
            <version>2.8</version>
            <inherited>false</inherited>
            <reportSets>
              <reportSet>
                <reports>
                  <report>checkstyle</report> <!-- editted 2012-05-01; was previously "checkstyle-aggregate" which was wrong -->
                </reports>
              </reportSet>
            </reportSets>
          </plugin>
      ...
    </plugins>
  </reporting>

[1] http://www.mailinglistarchive.com/html/users@maven.apache.org/2011-12/msg00134.html

Not sure that the reported fix to the count problem MCHECKSTYLE-167 has been fixed in the checkstyle-aggregate report. If you have a look at http://maven.apache.org/plugins/maven-checkstyle-plugin/project-reports.html, you will see the report repetition AND that the first report has double the issues of the second report. In the checkstyle-aggregate report, each error is reported twice.

The workaround works great (in terms of providing one report and removing the repeats), though I had to make a minor adjustment (my full config shown)...

  <reporting>
      ...
	<plugin>
           <groupId>org.apache.maven.plugins</groupId>
           <artifactId>maven-checkstyle-plugin</artifactId>
           <version>2.9</version>
	   <inherited>false</inherited>
	   <reportSets>
	     <reportSet>
		<reports>
		  <report>checkstyle</report>        <!-- This is changed from above -->
		</reports>
	     </reportSet>
	   </reportSets>
	   <configuration>
             <configLocation>group_default_checkstyles.xml</configLocation>
           </configuration>
         </plugin>
      ...

@Andrew: thanks, fixed incorrect copy-paste in my earlier comment.

Is there any update on this issue? I know we have workaround for this.
But it seems this issue is blocking the release of new version 2.10

Sorry, haven't had time to finish this yet.
There is no rush to get 2.10 out the door.

Our company wants to upgrade to Checkstyle5.6 for a new feature(accessing suppression file on network).
Since we are using maven in Jenkins for continious integration, we are looking forward to a coresponding upgrade in maven-checkstyle-plugin so that we can apply the upgrade to the whole company.
This issue is not critical from my perspective since we have a workaround.
So is it possible we can move this issue's fix to next release so that 2.10 would not be blocked.
Many thanks!

Fixed in r1438951.
I've taken care of the really simple single module case in this fix. Please give it a test.

If you have more advanced projects that generate an aggregate report when they shouldn't - please open a separate issue for that.

Thank you, Dennis!
BTW, when will 2.10 be release?

We need to release the plugins-parent first.
After that I'll release the maven-checkstyle-plugin 2.10.

So is it possible to have the new version this week? I just want to have a rough date to help me plan the upgrade. Thanks.