SONARJAVA-6235 Explicitely declare maven-bundle-plugin version to enable overriding

[tomasz-tylenda-sonarsource]

No description provided.

[sonar-review-alpha]

Summary

Extracts the hardcoded maven-bundle-plugin version (2.3.7) into a Maven property in the guava project's pom.xml. This allows the plugin version to be overridden at build time (e.g., via parent POMs, profiles, or CLI parameters) while maintaining the same default behavior.

The change is minimal and non-functional — the plugin continues to use version 2.3.7, but now through a property reference instead of a hardcoded value. This is a Maven best practice for plugin management.

What reviewers should know

What to look for:

• Single file change: guava/pom.xml
• Two modifications:
  1. New property maven-bundle-plugin.version added to <properties>
  2. Plugin <version> element updated to reference the property

Context:
The change addresses SONARJAVA-6235, which likely flags hardcoded plugin versions as a code quality issue. Extracting to a property is the standard Maven solution.

Risk assessment:
Minimal. This is a build configuration change with no impact on runtime behavior. The plugin version remains 2.3.7; only how it's specified changes. If other POM files (parent POMs, profiles) rely on overriding this version, they can now do so — verify this aligns with your build setup if version overrides are used elsewhere.

---

• Generate Walkthrough
• Generate Diagram

🗣️ Give feedback

[sonar-review-alpha]

LGTM! ✅

Clean, minimal change. No issues found.

🗣️ Give feedback