Skip to content

Keep the Maven wrapper on 3.9 for the Central publishing - #22

Merged
thomasdarimont merged 2 commits into
mainfrom
gh-21-maven-3.9-for-publishing
Oct 4, 2026
Merged

thomasdarimont merged 2 commits into
mainfrom
gh-21-maven-3.9-for-publishing

Conversation

@thomasdarimont

Copy link
Copy Markdown
Collaborator

Maven 3.10 (Resolver 2) writes _remote.repositories marker files into the staging directory the central-publishing-maven-plugin bundles, and Central rejects the bundle as content without a POM; the first release of 0.2.0 failed that way. Back to 3.9.16, Dependabot ignores minor and major Maven updates until the plugin excludes the files.

Closes #21

Maven 3.10 (Resolver 2) writes _remote.repositories marker files into
the staging directory the central-publishing-maven-plugin bundles, and
Central rejects the bundle as content without a POM; the first release
of 0.2.0 failed that way. Back to 3.9.16, Dependabot ignores minor and
major Maven updates until the plugin excludes the files.

Closes #21

Signed-off-by: Thomas Darimont <thomas.darimont@googlemail.com>
They name the tag of a release before it is pushed.

Signed-off-by: Thomas Darimont <thomas.darimont@googlemail.com>
@thomasdarimont
thomasdarimont merged commit 0020acc into main Oct 4, 2026
10 checks passed
@thomasdarimont
thomasdarimont deleted the gh-21-maven-3.9-for-publishing branch October 4, 2026 13:13
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.

Maven version 3.10. causes issues with the release process

1 participant