Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

4
  • Perfect. Just one thing: I had to add a <version>2.3.3</version> into the inner plugin to get rid of a maven warning message. Thanks Commented Dec 20, 2011 at 11:16
  • 2
    BTW, is it possible to have this rule run as part of the build life cycle? I'd like findbugs to fail builds if it finds something serious (it'll also need to generate the HTML report so I can find out what went wrong) Commented Dec 20, 2011 at 12:14
  • According to the plugin-website, there is a findbugs:check goal, that is binded to the verify phase by default and let the build fail by any error. But there will only xml output from this goal. Commented Dec 20, 2011 at 20:24
  • Thanks for the info. It explains why I've had so much trouble trying to get it to work! That's an odd and painful way to work - if findbugs is going to break the build (my requirement) then I'd like a human readable report to tell me why! Oh well... Commented Dec 21, 2011 at 8:57