PoC Changes for Checkstyle Metadata Integration

[gaurabdg]

Changes to introduce

• Create utility to override Repository with metadata values
• Create utility to create new Rules in the Repository if they are not present in rules.xml(it becomes kind of freezed when these are merged in master)
• For the above step, write a method to store plugin specific values in YAML.
• Add dynamic loading for acceptable tokens
• Add dynamic loading for enum values

[romani]

We do not need to automate generation of https://github.com/checkstyle/sonar-checkstyle/blob/master/src/main/resources/com/sonar/sqale/checkstyle-model.xml , this file has plugin specific values of grouping checks and placing some metadata on Check that is very specific to Sonar.
We can keep it as is.

Sonar resources:

Automate the process of creation of rules.xml

No need to generate such file.
So our goal is to make config file(s) to override all content from org.sonar package/folder.
Old format is loaded by RulesDefinitionXmlLoader, ExternalDescriptionLoader, we keep it as is, you make your method load metadata, and put all values from metadata objects to repository.

[romani]

Automate the generation of checkstyle-model.xml

No need.
here I see that it is not requiered. All we need to fill NewRepository repository with values from xml file, we can do this from any other file or already loaded POJO class.

So you need to keep that local from xml as is.

You also can notice that SqaleXmlLoader are deprecated so there is some changes in Sonar to load checkstyle-model.xml (grouping, remediationFunction, time estimations).
@muhlba91 , can probably can give more insight on future and requierments of this config. As I already mentioned it would be awesome to stop estimating time of fix and group Checks as Sqale wants. All Checks can go to some single group "maintenance", so it will ease our maintenance of this plugin a lot.