The previously-used version of the SonarQube plugin issued a warning notice, informing about a feature getting deprecated in the next version, whenever a gradle task was invoked.
A potential fix was to set the gradle.skipCompile flag to "true" upon calling a gradle function, but this is not ideal. The version of the plugin was updated entirely to avoid the warning notice, as well as to keep the plugins up-to-date in the application.
Checklist
[x] Code Formatter (run prettier/spotlessApply)
[x] Code has unit tests? (If no explain in _otherinformation)
[x] Builds on localhost
[x] Builds/Runs in docker compose
What is the current behavior?
Upon invoking any gradle task, the following message appeared:
The 'sonarqube' task depends on compile tasks. This behavior is now deprecated and will be removed in version 5.x. To avoid implicit compilation, set property 'sonar.gradle.skipCompile' to 'true' and make sure your project is compiled, before analysis has started.
The 'sonar' task depends on compile tasks. This behavior is now deprecated and will be removed in version 5.x. To avoid implicit compilation, set property 'sonar.gradle.skipCompile' to 'true' and make sure your project is compiled, before analysis has started.
What is the new behavior?
The message no longer appears since the version of SonarQube has been updated to the latest version.
Issue number: resolves #213
The previously-used version of the SonarQube plugin issued a warning notice, informing about a feature getting deprecated in the next version, whenever a gradle task was invoked.
A potential fix was to set the
gradle.skipCompile
flag to "true" upon calling a gradle function, but this is not ideal. The version of the plugin was updated entirely to avoid the warning notice, as well as to keep the plugins up-to-date in the application.Checklist
What is the current behavior?
Upon invoking any gradle task, the following message appeared:
What is the new behavior?
The message no longer appears since the version of SonarQube has been updated to the latest version.
Does this introduce a breaking change?
Other information
N/A