Maven 2.x FindBugs Plugin

empty surefire report at the project site having findBugs in the reporting section

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 2.3
  • Fix Version/s: 2.3.2
  • Component/s: None
  • Labels:
    None
  • Number of attachments :
    1

Description

findBugs in an reporting section seems to have an impact on the generation of the surefire-report of the project site. This report is empty

<reporting>
<plugins>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-surefire-report-plugin</artifactId>
<version>2.3</version>
</plugin
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-checkstyle-plugin</artifactId>
<version>2.4</version>
</plugin>
</plugins>
</reporting>

Activity

Hide
Garvin LeClaire added a comment -

More information would be beneficial. I cannot reproduce this with version 2.3 or 2.4-SNAPSHOT with any number of my projects or other Open Source projects.

Garvin

Show
Garvin LeClaire added a comment - More information would be beneficial. I cannot reproduce this with version 2.3 or 2.4-SNAPSHOT with any number of my projects or other Open Source projects. Garvin
Hide
christoph schmidt-casdorff added a comment -

Hi Garvin,

I uploaded an example showing the case

We use maven 2.2.1 and jdk 1.5 (we use enforcer-plugin)

If you call maven site on the project the resulting project-report contains an empty surefire-report.

There are two situations where the error doesn't occur

1) you have to delete the clean plugin from the build/plugins-section
2) you have to delete the findBugs-plugin from the reporting-section

Show
christoph schmidt-casdorff added a comment - Hi Garvin, I uploaded an example showing the case We use maven 2.2.1 and jdk 1.5 (we use enforcer-plugin) If you call maven site on the project the resulting project-report contains an empty surefire-report. There are two situations where the error doesn't occur 1) you have to delete the clean plugin from the build/plugins-section 2) you have to delete the findBugs-plugin from the reporting-section
Hide
Grzegorz Slowikowski added a comment -

I don't understand why Garvin closed this issue with FIXED status. There is no fix.
FindBugs is forking new Maven life cycle. You have:
<plugin>
<artifactId>maven-clean-plugin</artifactId>
<version>2.3</version>
<executions>
<execution>
<phase>initialize</phase>
<goals>
<goal>clean</goal>
</goals>
</execution>
</executions>
</plugin>
in your sample pom. This is wrong.
Every forking plugin will invoke clean before it's own execution.
This issue should be closed as WONT FIX.

Show
Grzegorz Slowikowski added a comment - I don't understand why Garvin closed this issue with FIXED status. There is no fix. FindBugs is forking new Maven life cycle. You have: <plugin> <artifactId>maven-clean-plugin</artifactId> <version>2.3</version> <executions> <execution> <phase>initialize</phase> <goals> <goal>clean</goal> </goals> </execution> </executions> </plugin> in your sample pom. This is wrong. Every forking plugin will invoke clean before it's own execution. This issue should be closed as WONT FIX.
Hide
Garvin LeClaire added a comment -

The issue is closed correctly. Test of the current version 2.3.2-SNAPSHOT produce a surefire report while the previous versions did not. This was tested on windows and osx. If you have different results please forward the project.

Garvin

Show
Garvin LeClaire added a comment - The issue is closed correctly. Test of the current version 2.3.2-SNAPSHOT produce a surefire report while the previous versions did not. This was tested on windows and osx. If you have different results please forward the project. Garvin

People

Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved: