-
Notifications
You must be signed in to change notification settings - Fork 69
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
update documentation after transfer #6
Comments
in case page of sonar-checkstyle mapping could disappear , backup is https://drive.google.com/open?id=0B3LUiB4ZPKNjalloQ0tEVl9tYmM |
from Michael:
we need to remove Deprecated |
deprecations were removed |
it is ok to skip this, I decided to do substitution instead of removal for now just to simplify my way to release. |
…tatus was removed)
…s deprecated ...' is removed from html files)
from email:
About the coverage report, you really don't need to keep it up-to-date or provide your own report. Simply remove it! If the report is not up-to-date, it's our problem. It should be Sonarsource work to keep the tracking "alive", as an internal tool. From a pure Checkstyle perspective, and as the new official maintainer of the plugin, I would invite you to :
Remove the now useless part about the rules which have been rewritten from the README.md file, including the link to the report:
A majority of the Checkstyle rules have been rewritten in the Java plugin. Rewritten rules are marked "Deprecated" in the Checkstyle plugin, but a concise summary of replaced rules is available.
Remove all the "DEPRECATED" status tags from the rules in the rules.xml file: https://github.com/checkstyle/sonar-checkstyle/blob/master/sonar-checkstyle-plugin/src/main/resources/org/sonar/plugins/checkstyle/rules.xml
Update all the rules description to remove the links to the sonarsource rules in this folder: https://github.com/checkstyle/sonar-checkstyle/tree/master/sonar-checkstyle-plugin/src/main/resources/org/sonar/l10n/checkstyle/rules/checkstyle
After all, you are now the rightful maintainer of the plugin, and I can't see why these rules should be marked as deprecated anymore. As the checkstyle plugin is not shipped anymore with SonarQube, a SonarQube user installing the checkstyle plugin won't be interested by having the mapping with the Sonarsource java rules.
I'm however pretty sure that if you could provide a list of rules from checkstyle wrongly mapped, someone at Sonarsource will be pretty happy. :)
Cheers,
Michael
The text was updated successfully, but these errors were encountered: