-
Notifications
You must be signed in to change notification settings - Fork 578
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
Some detectors broken since 4.5.3.0 #1919
Comments
@gtoison Interesting. I had a suspicion that things downstream could break due to tightening up the class name check, but hoped we would have been saved by test coverage. I'd like to point out that I'm not a spotbugs maintainer or long-term contributor - this was just a single patch to fix invalid rejection of edge-case Kotlin classes (with an attempt to actually get class name validation correct while I was there instead of just doing away with it altogether). Therefore, the views of the maintainers and long-term contributors may be different from mine on this topic, and will ultimately should have more weight. My views are my own as a one-off contributor and do not represent the project. Upon looking at the stack trace, I might be happy to analyse this further and either contribute a PR to either here or find-sec-bugs, but unfortunately, it will likely be many weeks before I will have time to do it. |
I raised the same issue over on I also raised a PR over there to resolve the issue - find-sec-bugs/find-sec-bugs#669 |
@scottsteen 🚀 Great work! Thanks for fixing this downstream. @KengoTODA - this issue can possibly be closed, as this will be fixed in find-sec-bugs/find-sec-bugs#669. |
With the same
pom.xml
, I get normal execution with4.5.2.0
, but switching to4.5.3.0
, I get some errors with some FindSecBugs detectors:pom.xml
plugins sectionThe text was updated successfully, but these errors were encountered: