Skip to content

Pin explicit Maven plugin versions in the project POM - #106

Open
bmarwell wants to merge 1 commit into
OpenHFT:eafrom
bmarwell:update_plugins
Open

Pin explicit Maven plugin versions in the project POM#106
bmarwell wants to merge 1 commit into
OpenHFT:eafrom
bmarwell:update_plugins

Conversation

@bmarwell

@bmarwell bmarwell commented Feb 3, 2026

Copy link
Copy Markdown

Add explicit plugin-management versions for compilation, tests, packaging, documentation and release tooling using the Maven Toolbox command recorded below. Remove the local build-helper version so it uses the new managed entry.

Review the generated version set against the parent POM and supported build JDKs. In particular, the diff adds a second maven-site-plugin entry alongside the existing one; reconcile that duplication and verify the effective model before accepting the plugin changes.

Validation: the diff and recorded review/check history were inspected at e97ccc55126d. No build, test or benchmark was rerun for this metadata edit. No CI result was returned for this head.


Existing author and review notes

Since the parent pom is always late with versions, here is a PR FYI (or for merging if you wish) which updated all the plugins.

Command used:

mvn eu.maveniverse.maven.plugins:toolbox:0.15.1:lock-plugin-versions -Dapply

@peter-lawrey peter-lawrey changed the title lock maven versions Pin explicit Maven plugin versions in the project POM Sep 12, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant