-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
NPE: Preconditions.checkNotNull #15
Comments
BTW, the java stuff is in there to get it to play nicely with the TFS SonarQube plugin - it's irrelevant otherwise. |
We had similar reports in the past with #6, and those weren't related to any exclusions -- at least none of the examples reported there had any. It looks like a paths problem. Specifically, the code that parses CFLint's XML output is trying to get a handle on the file for a given issue and most likely isn't finding it in the index of files of the sonar-scanner. What could help is, if you could attach here:
|
I'm running into the same issue scanning a reasonably large project. Unfortunately I can't share results because it's corporate code, but here's the stack trace:
|
Additional info: I was able to run CFLint successfully against Cold Fusion code that (one project) won't finish a Sonar scan without NPE: Preconditions.checkNotNull, and (another project) that scans into Sonar OK but doesn't let you drill down into the detailed issues - it shows zeros for each of the blocker, critical, major, minor and info issues, which doesn't match up with the summary stats. |
I'm getting an NPE running sonar-scanner with the following properties:
The problem goes away if I remove the exclusions. I have a feeling I've got a bad exclusion, but I'm not sure how to write it properly. If that is the case, it should throw a useful exception stating as such, not an NPE.
Sonar properties:
NPE Exception trace:
The text was updated successfully, but these errors were encountered: