nexus-staging-maven-plugin执行mvn deploy返回401无详情求助

I’ve run into similar head-scratching issues with the nexus-staging-maven-plugin before—especially when curl works but Maven doesn’t. Let’s break down actionable steps to debug exactly what’s going wrong:

1. Crank Up Maven’s Debug Logging (and Filter It) #

You mentioned using -X, but let’s focus specifically on the plugin’s traffic to cut through the noise. Run:

mvn deploy -X | grep -A 15 -B 15 "nexus-staging-maven-plugin"

This will isolate logs from the plugin, including:

• The exact server ID it’s trying to use (check if it matches the <id> in your settings.xml server entry)
• The full HTTP request URL it’s targeting
• Hints about the Authorization header being sent (or not sent)

If you don’t see the Authorization header at all, that’s a red flag—Maven isn’t picking up your server credentials.

2. Verify Your Effective Maven Settings #

Maven sometimes uses a different settings.xml than you expect (e.g., a global one instead of your user-specific ~/.m2/settings.xml). Run this to see the merged, effective settings:

mvn help:effective-settings

Look for the <servers> section and confirm:

• The <id> matches exactly the <id> in your pom’s <distributionManagement> entry (case-sensitive!)
• The <username> is your Sonatype access token ID, and <password> is the token’s secret
• No typos or extra whitespace in either value

3. Enable Verbose Mode in the Plugin #

Force the plugin itself to spit out more details by adding <verbose>true</verbose> to its configuration in your pom.xml:

<plugin>
  <groupId>org.sonatype.plugins</groupId>
  <artifactId>nexus-staging-maven-plugin</artifactId>
  <version>1.6.13</version> <!-- Use the latest recommended version -->
  <configuration>
    <serverId>ossrh</serverId> <!-- Match your settings.xml server id -->
    <nexusUrl>https://oss.sonatype.org/</nexusUrl>
    <verbose>true</verbose> <!-- Add this line -->
    <!-- Your other configs -->
  </configuration>
</plugin>

Now re-run mvn deploy -X—you’ll get granular details about every HTTP request the plugin makes, including full request/response headers and payload snippets. This often reveals if the plugin is using the wrong URL, or if the Authorization header is malformed.

4. Compare Curl and Plugin Requests Side-by-Side #

Since your curl command works, capture its full request details with:

curl -v -u YOUR_TOKEN_ID:YOUR_TOKEN_SECRET YOUR_UPLOAD_URL

Compare this to the plugin’s request logs from step 3. Look for differences in:

• The target URL (is the plugin hitting the staging repository, not a snapshot repo?)
• The Authorization header format (Sonatype expects Basic auth with your token ID/password)
• Request headers like Content-Type or User-Agent (rare, but sometimes plugins add headers that cause issues)

5. Rule Out Password Encryption Issues #

If you encrypted your token password in settings.xml, temporarily replace it with the plaintext token secret and re-run the deploy. If it works, your encryption setup has a problem (e.g., incorrect master password).

6. Upgrade the Plugin #

Old versions of the nexus-staging-maven-plugin have known bugs with authentication or URL handling. Check Sonatype’s docs for the latest recommended version and update your pom.xml accordingly.

Once you have the verbose logs, you’ll almost certainly spot the discrepancy—whether it’s a mismatched server ID, a wrong URL, or the plugin not picking up your credentials correctly.

内容的提问来源于stack exchange，提问作者Rolf