Fix Sonarcloud integration

[louisjdmartin]

Proposed changes

Fix sonarqube analysis in CI

Types of changes

What types of changes does your code introduce to this software?

Put an x in the boxes that apply

• Bugfix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation Update (if none of the other choices apply)

Checklist

Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.

• I have read the CONTRIBUTING doc
• I agree with the CODE OF CONDUCT
• Lint and unit tests pass locally with my changes
• SonarCloud and Travis CI tests pass with my changes
• I have added tests that prove my fix is effective or that my feature works
• I have added necessary documentation (if appropriate)
• Any dependent changes have been merged and published in downstream modules

[louisjdmartin]

Must be squashed on merge
@Topin2001 can you review it? (on friday :) )

[Topin2001]

Is it mandatory to keep java 11 in the matrix ? Since we are only using 17 (if I'm correct)

[sonarqubecloud]

Quality Gate passed

Kudos, no new issues were introduced!

0 New issues
0 Security Hotspots
No data about Coverage
No data about Duplication

See analysis details on SonarCloud