Hi

I have as you a top "corporate" pom which defines all versions on the plugings.
Maven itsels is at 3.0.2, findbugs is on latest  2.4 , emma is the latest 1.0-alpha-3, the site plugin is actually only 3.0-beta-3. Dashboard is on 1.0.0-beta-1 which seems to be the latest.

But really I like to have an "aggregated" view of how many findbugs bugs we have instead of be forced to drill down on each subproject to see the status.

right now I am running "mvn install site dashboard:dashboard site:stage-deploy"
but not all reports gets included in the "site". For instance the findbugs reports.

But if a run "mvn install site dashboard:dashboard" and have the dashboard to a separate folder then it will show an aggregate view of findbugs bugs...

Maybe the issue is simply the old site plugin...

But, Thorsten, are you able to have an aggregate code coverage report using for instance Emma or JaCoCo using the site plugin?
(Emma and JaCoCo have nice Eclipse plugins and that's why we do not use Cobertura or Clover)

/Lucas
PS

My reports section (in the root pom) looks like this:
  <reporting>
    <outputDirectory>${targetDirectory}/site</outputDirectory>
    <plugins>

      <!-- Basic reports for all poms -->
      <plugin>
        <groupId>org.apache.maven.plugins</groupId>
        <artifactId>maven-project-info-reports-plugin</artifactId>
        <version>${oracle.sdp.maven-project-info-reports-plugin.version}</version>
        <inherited>true</inherited>
        <reportSets>
          <reportSet>
            <inherited>true</inherited>
            <reports>
              <report>index</report>
              <report>dependencies</report>
            </reports>
          </reportSet>
        </reportSets>
      </plugin>
      <!-- Second definition of plugin above, generate extra report for root POM _only_ -->
      <plugin>
        <groupId>org.apache.maven.plugins</groupId>
        <artifactId>maven-project-info-reports-plugin</artifactId>
        <version>${oracle.sdp.maven-project-info-reports-plugin.version}</version>
        <inherited>false</inherited>
        <reportSets>
          <reportSet>
            <id>onlyRootReport</id>
            <inherited>false</inherited>
            <reports>
              <report>dependency-convergence</report>
            </reports>
          </reportSet>
        </reportSets>
      </plugin>
      <!-- Basic site plugin from maven -->     
      <plugin>
        <groupId>org.apache.maven.plugins</groupId>
        <artifactId>maven-site-plugin</artifactId>
        <version>${oracle.sdp.maven-site-plugin.version}</version>
        <inherited>true</inherited>
        <configuration>
          <outputEncoding>utf-8</outputEncoding>
          <outputDirectory>${targetDirectory}/site</outputDirectory>
          <stagingSiteURL>${project.distributionManagement.site.url}</stagingSiteURL>
        </configuration>
      </plugin>
     
      <!-- Surefire plugin (JUnit runner) -->
      <plugin>
        <groupId>org.apache.maven.plugins</groupId>
        <artifactId>maven-surefire-report-plugin</artifactId>
        <version>${oracle.sdp.maven-surefire-report-plugin.version}</version>
        <inherited>true</inherited>
        <configuration>
          <showSuccess>true</showSuccess>
          <outputDirectory>${targetDirectory}/site</outputDirectory>
          <reportsDirectory>${targetDirectory}/surefire-reports</reportsDirectory>
        </configuration>
      </plugin>


      <!-- Taglist report -->
      <plugin>
        <groupId>org.codehaus.mojo</groupId>
        <artifactId>taglist-maven-plugin</artifactId>
        <version>${oracle.sdp.taglist-maven-plugin.version}</version>
        <inherited>true</inherited>
        <configuration>
          <aggregate>true</aggregate>
            <tags>
              <tag>TODO</tag>
              <tag>FIXME</tag>
              <tag>@todo</tag>
            </tags>
          </configuration>
      </plugin>
      <!-- Package dependency report -->
      <plugin>
        <groupId>org.codehaus.mojo</groupId>
        <artifactId>jdepend-maven-plugin</artifactId>
        <version>${oracle.sdp.jdepend-maven-plugin.version}</version>
        <inherited>true</inherited>
      </plugin>

      <!-- FindBugs (Java class file static analysis) -->
      <plugin>
        <groupId>org.codehaus.mojo</groupId>
        <artifactId>findbugs-maven-plugin</artifactId>
        <version>${oracle.sdp.findbugs-maven-plugin.version}</version>
        <inherited>true</inherited>
        <configuration>
          <fork>false</fork>
          <xmlOutput>true</xmlOutput>
          <effort>Max</effort>
          <excludeFilterFile>${adeViewRoot}/sdp/tools/maven/oracle_findbugs_exclusion_rules.xml</excludeFilterFile>
        </configuration>
      </plugin>

      <plugin>
        <groupId>org.codehaus.mojo</groupId>
        <artifactId>dashboard-maven-plugin</artifactId>
        <version>${oracle.sdp.dashboard-maven-plugin.version}</version>
      </plugin>
    </plugins>
  </reporting>




On 03/07/2012 02:14 PM, Thorsten Heit wrote:
Hi,

I am in search for a nice way to compile all reports for a Maven build.
I have for instance JUnit results, findbugs results and code coverage
results (using Emma).

The maven site plugin does not really aggregate info so that I can get
the total number of findbugs bugs so I started to look at the dashboard
plugin from codehaus, but that plugin does not seem to get developed any
more. And there is not way to support Emma in it either.
What does your pom look like? And what version of Maven, site/findbugs/... 
plugins do you use?

On my system I'm using a corporate parent pom containing a couple of 
profiles that, when activated, add Findbugs, Checkstyle and/or PMD reports 
to the generated website. Works pretty fine.


Regards

Thorsten

--
Oracle
Lucas Persson | Principal Member of Technical Staff
Phone: +4684773644 | | | Mobile: +46730946656
Oracle Communications Platform
ORACLE Sweden | Söder Mälarstrand 29, 6 tr | 118 25 Stockholm


Oracle Svenska AB, Kronborgsgränd 17, S-164 28 KISTA, reg.no. 556254-6746
Green
          Oracle Oracle is committed to developing practices and products that help protect the environment

Reply via email to