-
Notifications
You must be signed in to change notification settings - Fork 363
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
How to solve "The SonarQube plugin declaring this property should be updated" #1775
Comments
Hi @Lenegred, thanks for the feedback. This issue is known and because of SQ API changes. This warnings is to update the plugin code but should have no impact on the functionality. With next plugin release (supports SQ 7.9 LTS only) we have to clean-up/remove all deprecated APIs. Regards, |
I'm still seeing this in Feb 2022 on an Android project with Sonar plugin v3. Is that expected? |
@cheskos what do you mean with V3? Which versions of the cxx plugin and SonarQube are you using? |
I see these warnings too. I have sonarqube plugin version 3.3.
|
Hi @atipal , is this the right forum. This is the cxx plugin and there is no plugin version 3.3? |
I have met a problem at using ths plugin sonar-c-plugin-1.3.1.1807.jar .
When the jenkins start analyzing prossess,this problem will happen as follow logs.
WARN: Property 'sonar.c.includeDirectories' is not declared as multi-values/property set but was read using 'getStringArray' method. The SonarQube plugin declaring this property should be updated.
WARN: Property 'sonar.c.forceIncludes' is not declared as multi-values/property set but was read using 'getStringArray' method. The SonarQube plugin declaring this property should be updated.
WARN: Property 'sonar.c.cFilesPatterns' is not declared as multi-values/property set but was read using 'getStringArray' method. The SonarQube plugin declaring this property should be updated.
The prossess seized up.
What should I to do ? Logs tell me to update this plugin.But the version 1.3.1 is the lastest.
Thanks.
The text was updated successfully, but these errors were encountered: