-
Notifications
You must be signed in to change notification settings - Fork 29
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
Sonar Deprecation #32
Comments
Hi, Thanks for reporting. Yes, I know about that. If I'm not wrong, you meet this issue as of SQ 7.3. I keep this metrics however because the plugin is compatible with SQ 6 and it is relevant for this version. The API doc says that "measures are no longer sent within analysis reports" so I have to fix that in a next release but to be honest the SonarQube documentation is pretty poor and has not helped me so far find the proper to replace the way I calculate measures in my plugin. If you have some inputs on this, I'll be very happy. Regards |
According to https://community.sonarsource.com/t/as-of-7-3-what-is-the-proper-way-to-calculate-the-comment-lines-data-measure/11712/2, my code is already doing the right thing (meaning, using COMMENT_LINES), so the warning can be safely ignored. |
Then please send this metric depending on Sonar version. See this doc: |
Sorry but what is wrong with this warning? As far as I know it appears in the scanner output so you can just ignore it? |
We have a zero warning policy, so we try to avoid getting warnings if possible. Normally a warning should indicate that something might be wrong which is not the case here. |
OK, it makes sense, I'll do that. Implementing the checks for such a policy could take some times, I hope you are not in a rush. |
With Sonar 7.9 LTS and Yaml Plugin 1.4.3 I get the following deprecation warning:
This seems to come from LineCounter class using CoreMetrics.COMMENT_LINES_DATA_KEY.
The text was updated successfully, but these errors were encountered: