Details
Description
There are several use cases for that.
1. Delete rules extensions which are removed from definition XML file
The server loads at startup /extensions/rules/checkstyle|pmd/*.xml files which define rules extensions. If a rule is removed from a XML, it should also be removed from the web interface.
2. When removing a plugin that has got a rule repository, the rules should be removed from the database. Otherwise it can have some whereas profiles will still display them in the total count of active rules for the profile
Issue Links
- is duplicated by
-
SONAR-1124
Issue with importing Findbugs profile
-
-
SONAR-459
Coding rules are not deleted from database when they are removed from XML repositories
-
I think I have a similar issue to this: I added a new rule for a new Checkstyle check to the xml file, but the classname was wrong. It appears you cannot remove the invalid rule and it keeps giving ClassNotFoundExeptions looking for the wrong class (when running the mvn sonar:sonar target).
The modified rule with the correct class name is treated as a new rule, so now I have one rule pointing to a class that doesn't exist, and a different rule that points to the correct class. I don't have exact recreation steps at this point because we're trying to work out how we got to where we are and how to get back to a working config
but if I find out more I'll post an update