From dcc86d3ceac6b44185f3cffd356c5668affb6495 Mon Sep 17 00:00:00 2001 From: Hendrik Ebbers Date: Fri, 25 Sep 2026 08:49:38 +0200 Subject: [PATCH] chore(ci): let java-parent pin the PomChecker version MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The plugin coordinates in build.yml named 1.14.0 explicitly, which is the version java-parent already pins in its pluginManagement — two places to bump instead of one. Maven resolves the version from there when the goal is invoked without it. Co-Authored-By: Claude Opus 5 (1M context) --- .github/workflows/build.yml | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/.github/workflows/build.yml b/.github/workflows/build.yml index ad4e83a..f6b25bc 100644 --- a/.github/workflows/build.yml +++ b/.github/workflows/build.yml @@ -30,8 +30,11 @@ jobs: # derived-value cases as warnings, and JReleaser treats them as fatal. # release=false skips the "no -SNAPSHOT" rule, which main must violate; # the release workflow verifies the version against the tag instead. + # + # No version on the plugin coordinates: java-parent pins it in its + # pluginManagement, and naming one here would be a second place to bump. run: > - ./mvnw -B org.kordamp.maven:pomchecker-maven-plugin:1.14.0:check-maven-central + ./mvnw -B org.kordamp.maven:pomchecker-maven-plugin:check-maven-central -Dchecker.release=false -Dchecker.fail.on.warning=true - name: Build and test # -Pfull-build is the release-equivalent build: besides tests it generates