The SonarScanners download only required 3rd-party plugins

[guwirth]

SonarQube 10.4 will come with a feature to only download Sonar analyzers and 3rd-party plugins when they are really required by the Scanner. To make this feature work, each analyzer or 3rd-party plugin should declare the list of languages on which they expect to raise issues through a new MANIFEST property called Plugin-RequiredForLanguages.

In SonarQube 10.4, this feature will be disabled by default to give you, plugin maintainers, time to adjust the configuration of your plugins. It will be activated by default with SonarQube 10.5.

https://community.sonarsource.com/t/the-sonarscanners-download-only-required-3rd-party-plugins/108156

Advanced build properties
Plugin properties are defined in the file META-INF/MANIFEST.MF of the plugin jar file.

requiredForLanguages: Languages for which this plugin should be downloaded. Use to make sure dependency errors are avoided when the loading of analyzers is optimized. This property must be added to the section of the plugin’s pom.xml file.

For an example, see this configuration for Java.

[guwirth]

See also https://community.sonarsource.com/t/the-sonarscanners-download-only-required-3rd-party-plugins/108156/9

<requiredForLanguages>js,ts,web,yaml</requiredForLanguages>

This would be the expected syntax when using maven to declare multiple languages for a plugin.