-
Notifications
You must be signed in to change notification settings - Fork 7.6k
1.x: Add Findbugs #4099
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
1.x: Add Findbugs #4099
Conversation
Current coverage is 80.28%@@ 1.x #4099 diff @@
==========================================
Files 258 258
Lines 16834 16834
Methods 0 0
Messages 0 0
Branches 2549 2549
==========================================
- Hits 13529 13515 -14
- Misses 2400 2408 +8
- Partials 905 911 +6
|
Running FindBugs locally shows me 31 problems. Half of them look valid, the other half can be ignored (although I don't see any obvious way of suppressing a warning at a specific source line). |
Suppressing them is kind of weird AFAIK you can't use |
Is there an option to suppress them by XML file? (Yeah it's annoying, but On Fri, 24 Jun 2016, 01:05 Niklas Baudy, [email protected] wrote:
|
AFAIK you can just use the |
Could you rebase this? |
Done. |
👍 |
Continuing from #3164 .
Parsing the generated Findbugs output file it not as trivial as with PMD since it does contain some meta information.
Let me know whether this is wanted or not and if so how it can be pursued.
By default all rules from Findbugs are enabled and one can opt out using
excludeFilter = file('findbugs-filter.xml)
inside thefindbugs
block, which will then contain something alone the lines of this.