From d0dd256744a32a5d831957fd5fb8ce34adb2fa34 Mon Sep 17 00:00:00 2001 From: extio-de Date: Sat, 17 Oct 2026 21:27:58 +0200 Subject: [PATCH] fix: pin Maven 3.9.16 in publish workflow Maven 3.10 leaves _remote.repositories and maven-metadata files in the staging dir, which central-publishing-maven-plugin bundles into the deployment. Central then rejects the release with 'Bundle has content that does NOT have a .pom file: de/extio/lm-lib'. Pin the setup-java Maven version until upstream handles 3.10. --- .github/workflows/maven-publish.yml | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/.github/workflows/maven-publish.yml b/.github/workflows/maven-publish.yml index 941682a..d6c59fc 100644 --- a/.github/workflows/maven-publish.yml +++ b/.github/workflows/maven-publish.yml @@ -27,6 +27,10 @@ jobs: with: java-version: '25' distribution: 'temurin' + # Maven 3.10 leaves _remote.repositories / maven-metadata files in the + # staging dir and central-publishing-maven-plugin bundles them, so + # Central rejects the deployment. Keep pinned until upstream is fixed. + maven-version: '3.9.16' server-id: central server-username: MAVEN_USERNAME server-password: MAVEN_PASSWORD