Skip to content
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

No files to analyze could be opened #69

Open
Wuaner opened this issue Jan 19, 2015 · 1 comment
Open

No files to analyze could be opened #69

Wuaner opened this issue Jan 19, 2015 · 1 comment

Comments

@Wuaner
Copy link

Wuaner commented Jan 19, 2015

For a merge commit that no java file involved, belowing exception will throwed:

There is a problem with FindBugs: IOException: No files to analyze could be opened.

I think if it's a better idea that not throw exception for this scenario, because this is pretty normal situation for merge commit.

@AlanHohn
Copy link
Contributor

This seems to have come in when support was added for global problems collection (75b30e1). The previous behavior was to suppress an IOException.

Not sure if there are downsides to suppressing IOException (i.e. real errors from Findbugs) but it sure is annoying to have it posting this "problem" report when it shouldn't. I'm happy to submit a pull request to put the previous behavior back - worth a discussion at least.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants