-
Notifications
You must be signed in to change notification settings - Fork 136
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
Errors occurred during analysis using v3.5 #114
Comments
Few things needed for investigation:
|
Thanks for your response
Yes
Its about 500 lines of code and proprietary
Will do this and post result I also get some other errors common to other projects, but the scan also completes (find below)
|
@olaoluphilip Thanks for the update. To test "FindBugs-3.0.1" simply scan the same project with previous version of the plugin 3.4 (if you have not already) |
I did a couple of test with Java8 functional samples but could not reproduce this error state. Since, you can't share the code, you will need to do a bit more work : identify the bogus code and anonymize it. If you are afraid about leaking the code (even once anonymized), you can contact me at |
@olaoluphilip Without code to reproduce the issue, it will be close. Please take a moment to extract the appropriate code sample. |
Code received .. Trying to reproduce. |
Also a quick addition. I did this analysis using Sonarqube v6.3 |
I did not reproduce the bug yet. The release is still happening because it is not a blocker. This seems to affect specific Java 8 code structure. Sonar-FindBugs will be update when Spotbugs newer release will fix it. TLDR: Still trying to reproduce. It will not stop the release. |
In case its helpful-- I hit this on macOS High Sierra, Java 10, Gradle 4.8.1, Spotbugs-Plugin 1.6.2, IntelliJ 2017.3 but it resolved itself automatically on the next run without any changes. It could be some sort of race condition or conflict with the IDEA (IntelliJ with gradle auto-import is pretty aggressive). |
This issue seems to be stale, please feel free to open a new one or to comment here if needed |
The text was updated successfully, but these errors were encountered: