Skip to content
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

The SonarScanners download only required 3rd-party plugins #2648

Closed
guwirth opened this issue Mar 7, 2024 · 2 comments
Closed

The SonarScanners download only required 3rd-party plugins #2648

guwirth opened this issue Mar 7, 2024 · 2 comments
Milestone

Comments

@guwirth
Copy link
Collaborator

guwirth commented Mar 7, 2024

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 guwirth mentioned this issue Mar 8, 2024
@guwirth guwirth added this to the 2.2.0 milestone Mar 18, 2024
@guwirth
Copy link
Collaborator Author

guwirth commented May 15, 2024

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.

@guwirth
Copy link
Collaborator Author

guwirth commented Aug 20, 2024

closed with #2715

@guwirth guwirth closed this as completed Aug 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

1 participant