Maven findbugs 'high water mark'

Question

[findbugs is an example here, the question applies to any such maven plugin]

Recently I attended a lecture on assembly, and we talked about what I really liked: when you add a new tool to the chain and start with n violations, you should continue to n decrease (high water sign) and assembly failure only if the current check exceeds the last value of n.

findbugs was just introduced to our assembly, and we were looking for a way to implement this template. We could not see any way to do this through the configuration of the plugins, so it was curious if anyone out there could mention how they achieved this. I suppose the obvious way is to set up the plugin, but before we start charging, I would like to hear thoughts from others.

Answer 1

I raised this issue in maven findbugs trackers (see http://jira.codehaus.org/browse/MFINDBUGS-115 ).

Further, as part of this, I encoded the submitted patch. We successfully use this patch in our large multi-module project.

You can synchronize the code and apply the fix by following the instructions on the findbugs-maven-plugin website or, hopefully, the patch or its output can be accepted in some future version of the plugin.

Answer 2

Findbugs ( , ) XML . , maven, xml . -, , .

, . :

<plugin>
    <groupId>com.yourcompany</groupId>
            <artifactId>your-plugin-id</artifactId>
            <version>1.0</version>
            <executions>
                    <execution>
                        <id>readmetrics</id>
                        <phase>process-classes</phase>
                        <goals>
                            <goal>analyse-metrics</goal>
                        </goals>
                    </execution>
             </executions>
             <configuration>
                  <metrics>
                      <metric>
                          <type>findbugs</type>
                          <file>${project.reporting.outputDirectory}/findbugs/output.xml</file>
                      </metric>
                      <metric>
                          <type>checkstyle</type>
                          <file>${project.reporting.outputDirectory}/checkstyle/output.xml</file>
                      </metric>
                      <metric>
                          <type>pmd</type>
                          <file>${project.reporting.outputDirectory}/pmd/output.xml</file>
                      </metric>
                  </metrics>
              </configuration>
        </plugin>

Answer 3

FindBugs, , : , , , (.. High).

, ( ), Maven ( ). Sonar ( ). , , .

Answer 4

, , . , dybdob; , , /. , , , seanizer: XML, .

, ( : hardcoded, hacky ), , javac, , , . , , checkstyle pmd.

I would like you to find out, and write to me if you are interested in help (or even just want to see how it develops).