-
Notifications
You must be signed in to change notification settings - Fork 360
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
Associate issues with project / directory instead of file #80
Comments
Tought there was already a pull request for this one, but his can be done easily in the save violation method and will be available for all sensors |
PC-Lint sensor can write issues on Project level after adding additional function to CxxReportSensor class.
And modification of the PC-Lint sensor as well ( a snippet) :
and the check for the rule looks now like this:
I will run more tests for this improvement and create a pull request for PC-Lint plugin next weekend. |
While at it, we should handle file-level violations as well. |
This solution throws an NullPointerException for CppCheck, PC-Lint and Compiler (MSVC) results.
|
Handle file not found condition - skipping violation was not handle correctly
Handle file not found condition - skipping violation was not handle correctly
Handle file not found condition - skipping violation was not handle correctly
Handle file not found condition - skipping violation was not handle correctly
Handle file not found condition - skipping violation was not handle correctly
Handle file not found condition - skipping violation was not handle correctly
Handle file not found condition - skipping violation was not handle correctly
Hello,
This is a request to add violations without source code dependency.
Background is, that we are using analyzer generating project violations without source code or line information. We have the need to assign this violations to the project.
As an example - Clirr plugin does this: http://docs.codehaus.org/display/SONAR/Clirr+Plugin
context.saveViolation(Violation.create(activeRule,
resource).setMessage(violation.getMessage()));
This needs to be handled to all sensors, not only for the external sensor. I think at least the pc-lint also reports violations at project level.
See also
http://sonarqube.15.x6.nabble.com/Possible-to-add-violations-without-source-code-dependency-tp5014779.html
Regards
The text was updated successfully, but these errors were encountered: