Skip to content

Disable conflicting Nexus Staging plugin#10

Merged
jkebinger merged 1 commit intomainfrom
disable-nexus-staging-plugin
Sep 22, 2025
Merged

Disable conflicting Nexus Staging plugin#10
jkebinger merged 1 commit intomainfrom
disable-nexus-staging-plugin

Conversation

@jkebinger
Copy link
Copy Markdown
Contributor

Summary

Fix publishing failure by disabling the old nexus-staging-maven-plugin that conflicts with the new central-publishing-maven-plugin.

Problem

The basepom parent automatically enables nexus-staging-maven-plugin, which tries to run after central-publishing completes, causing:

Server credentials with ID "sonatype-nexus-staging" not found!

Solution

  • Add basepom.nexus-staging.skip=true property
  • Configure skipNexusStagingDeployMojo=true in plugin configuration
  • This allows only the central-publishing-maven-plugin to handle deployment

Test Results

Central Repository publishing was successful:
✅ 13 files staged successfully
✅ All checksums generated
✅ GPG signatures created

🤖 Generated with Claude Code

Add skipNexusStagingDeployMojo=true to prevent the old nexus-staging-maven-plugin
from running alongside the new central-publishing-maven-plugin.

Fixes "Server credentials with ID sonatype-nexus-staging not found" error.

🤖 Generated with [Claude Code](https://claude.ai/code)

Co-Authored-By: Claude <noreply@anthropic.com>
Copy link
Copy Markdown
Contributor

@jdwyah jdwyah left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

thanks

@jkebinger jkebinger merged commit e15cca1 into main Sep 22, 2025
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

2 participants