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

mark inconclusive messages in cppcheck V2 #429

Merged
merged 1 commit into from
Apr 5, 2015
Merged

mark inconclusive messages in cppcheck V2 #429

merged 1 commit into from
Apr 5, 2015

Conversation

guwirth
Copy link
Collaborator

@guwirth guwirth commented Feb 21, 2015

@guwirth guwirth added this to the M 0.9.3 milestone Feb 22, 2015
@guwirth guwirth self-assigned this Feb 22, 2015
@guwirth
Copy link
Collaborator Author

guwirth commented Feb 25, 2015

Was also wondering first. Background is that the reports in format V1 and V2 contain the same issues (file, line and msg). The plugin is filtering them and adds it only once. Starting with this feature there is additional text at the beginning of the message text (V1 without and V2 with inconclusive). Means they are different now.

- add [inconclusive] at the beginning of the message
- close #247
wenns added a commit that referenced this pull request Apr 5, 2015
…usive

mark inconclusive messages in cppcheck V2
@wenns wenns merged commit d865f8a into SonarOpenCommunity:master Apr 5, 2015
@guwirth guwirth deleted the enhancement/247_cppcheck_inconclusive branch April 14, 2015 10:19
@guwirth
Copy link
Collaborator Author

guwirth commented Apr 25, 2015

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

Successfully merging this pull request may close these issues.

Inconclusive issues from cppcheck not marked
2 participants