Skip to content

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

Merged
merged 1 commit into from
Jun 25, 2016
Merged

1.x: Add Findbugs #4099

merged 1 commit into from
Jun 25, 2016

Conversation

vanniktech
Copy link
Collaborator

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 the findbugs block, which will then contain something alone the lines of this.

@akarnokd akarnokd added the Build label Jun 23, 2016
@akarnokd
Copy link
Member

Thanks! I'd like to merge #4091 and #4092 first as rebasing this PR is much easier.

@codecov-io
Copy link

codecov-io commented Jun 23, 2016

Current coverage is 80.28%

Merging #4099 into 1.x will decrease coverage by 0.08%

@@                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   

Powered by Codecov. Last updated by d855a29...4af7438

@akarnokd
Copy link
Member

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).

@vanniktech
Copy link
Collaborator Author

Suppressing them is kind of weird AFAIK you can't use @SuppressWarnings, however there's a package, com.google.code.findbugs:annotations:3.0.1 which gives you @SuppressFBWarnings.

@artem-zinnatullin
Copy link
Contributor

Is there an option to suppress them by XML file? (Yeah it's annoying, but
should help).

On Fri, 24 Jun 2016, 01:05 Niklas Baudy, [email protected] wrote:

Suppressing them is kind of weird AFAIK you can't use @SuppressWarnings,
however there's a package, com.google.code.findbugs:annotations:3.0.1
which gives you @SuppressFBWarnings
http://findbugs.sourceforge.net/api/edu/umd/cs/findbugs/annotations/SuppressFBWarnings.html
.


You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
#4099 (comment),
or mute the thread
https://github.com/notifications/unsubscribe/AA7B3HRx3eid7aXe2iqRvGH99cZzuKP3ks5qOwM2gaJpZM4I9Rdz
.

@vanniktech
Copy link
Collaborator Author

AFAIK you can just use the excludeFilter and then inside ignore certain things (the same way we did it in QualityMatters with Butterknife).

@akarnokd
Copy link
Member

Could you rebase this?

@vanniktech
Copy link
Collaborator Author

Done.

@akarnokd
Copy link
Member

👍

@akarnokd akarnokd merged commit a6d6ba9 into ReactiveX:1.x Jun 25, 2016
@vanniktech vanniktech deleted the 1.x_findbugs branch July 23, 2018 13:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants