Standalone SonarQube plugin

[utarwyn]

Description

Its time to take the ecoCode JavaScript plugin to the next level! 🚀
The main objective of this PR is to create a standard SonarQube plugin that can be integrated into their marketplace.

Thanks to these changes, both plugins can now run completely independently. Rules are both displayed in the SonarQube interface and reported by ESLint. Boom! 💥

I'm taking the opportunity to move the SonarQube plugin from the main repository.

Changes

• Create SonarQube plugin (based on SonarJS)
• Pack ESLint plugin into SonarQube plugin
• Backport all existing rules into SonarQube plugin
• Update release process through GitHub Actions
• Update README
• Update CONTRIBUTING
• Add tooling files (copied from main ecoCode repository)

Actual / After

Actual 🐌🐌

Rules are loaded as external rules (more info here), so they are not displayed in the interface. They also can't be enabled/disabled or added to a quality profile. Users must manually install the ESLint plugin inside JS projects and update properties of the analyzer to include the ESLint report.

After 🔥🔥

The SonarQube plugin packs everything! No more manual task needed: rules are displayed in the interface like others. ESLint plugin can still be used alone in a project that does not use SonarQube.

Related Issues

Resolves #12

[utarwyn]

Here we go, the big rework is finished!

@glalloue @dedece35 if you want to read at least the SonarQube plugin (Java) part 😉
@jycr I have used EC8, EC9, EC11, EC12 and EC13 for existing rule keys but I think we need to talk about it

[jycr]

@jycr I have used EC8, EC9, EC11, EC12 and EC13 for existing rule keys but I think we need to talk about it

Those identifiers are currently not used. So no problem in my opinion to use these.

[jycr]

@jycr I have used EC8, EC9, EC11, EC12 and EC13 for existing rule keys but I think we need to talk about it

Those identifiers are currently not used. So no problem in my opinion to use these.

I have added those rules into: green-code-initiative/creedengo-rules-specifications#178

[jycr]

@utarwyn : if you want, you can remove rule specification files (in sonar-plugin/src/main/resources/io/ecocode/rules) and use following dependency:

        <dependency>
            <groupId>io.ecocode</groupId>
            <artifactId>ecocode-rules-specifications</artifactId>
            <version>0.0.1</version>
            <classifier>javascript</classifier>
        </dependency>

Also, I think you can make a PR to green-code-initiative/ecoCode project to remove module javascript-plugin

[utarwyn]

@jycr
if you want, you can remove rule specification files

Nice idea! Thank you for the artifact, I will try and create a new PR with the change

Also, I think you can make a PR to green-code-initiative/ecoCode project to remove module javascript-plugin

Yes I have planned to remove the javascript-plugin inside ecoCode right after this one will be merged

[utarwyn]

@dedece35 I have answered all your remarks/questions I think 😄

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

97.4% Coverage
0.0% Duplication

[dedece35]

ok for me, now.