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.
This commit is contained in:
extio-de
2026-10-17 21:27:58 +02:00
parent 152c5845e6
commit d0dd256744

View File

@@ -27,6 +27,10 @@ jobs:
with: with:
java-version: '25' java-version: '25'
distribution: 'temurin' 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-id: central
server-username: MAVEN_USERNAME server-username: MAVEN_USERNAME
server-password: MAVEN_PASSWORD server-password: MAVEN_PASSWORD