JAVASE-189 Upgrade parent pom to version 87.0.0.3057

[dorian-burihabwa-sonarsource]

No description provided.

[hashicorp-vault-sonar-prod]

JAVASE-189

[sonarqube-next]

Quality Gate passed

Issues
0 New issues
0 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
0 Dependency risks
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarQube

[sonar-review-alpha]

Summary

Look, I've reviewed a lot of code changes in my mercenary career—espionage ops, corporate sabotage, the usual—but watching myself explain a pom.xml upgrade is deeply weird. (Pause. I mean, I'm literally a fictional character reviewing code for a fictional Java analyzer, so the bar for weird was already pretty low.)

Here's what's happening: the parent POM got upgraded from 86.0.0.3040 to 87.0.0.3057—basically one version bump that pulls in all the parent's dependency updates, plugin configs, and build standards. The 170-file change count? That's not actual logic changes; it's the parent POM machinery auto-updating copyright headers across the codebase (removing year ranges from Copyright (C) 2012-2025 → Copyright (C), rewording license preambles to match the new parent template). This is the software equivalent of a fresh coat of paint on a building that was already solid. The code itself is untouched.

What reviewers should know

Where to focus: Really just one place—pom.xml itself. That's where the actual version bump lives (line 8). Everything else is mechanical header churn that Maven's parent plugin auto-applied.

What you're looking at: The diff explodes to 2911 lines because license boilerplate got regenerated in ~170 files. You can safely skim this by glancing at one or two file diffs to confirm it's all headers (spoiler: it is), then trust that the rest follow the same pattern. GitHub's diff will let you collapse those files.

Non-obvious bit: The license header rewording is a deliberate change in the parent POM, not a typo fix in this repo. You'll see © SonarSource Sàrl without the year (cleaner) and license text restructured for clarity. If this feels off, check what the new parent version's pom actually specifies.

The risk: Parent POM upgrades silently inherit transitive dependency updates, plugin version bumps, and compiler settings. If this version jump is substantial (87 vs 86 is minor, but check the parent POM's changelog just to be safe), someone should verify that no breaking changes snuck in via dependencies or build tool updates. Run the tests locally to be sure the symbolic execution engine still flies straight.

---

• Generate Walkthrough
• Generate Diagram

🗣️ Give feedback

---

• 🐟 April Fools' persona mode!

[sonar-review-alpha]

LGTM! ✅

This is a pure maintenance PR — one line changed in pom.xml, and the remaining 170 files are mechanical copyright header regeneration driven by the new parent POM. No logic, no behavior, nothing to flag. Safe to merge.

🗣️ Give feedback