Bug 1058572

Summary: Maven deploy ignores authentication
Product: [Fedora] Fedora Reporter: philnate
Component: mavenAssignee: Mikolaj Izdebski <mizdebsk>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 19CC: akurtako, java-sig-commits, mizdebsk, msrb, philnate, rmay, sochotni
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-05-12 05:02:46 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Maven deploy failure for provided version and success for version from Apache none

Description philnate 2014-01-28 04:46:48 UTC 
Created attachment 856364 [details]
Maven deploy failure for provided version and success for version from Apache

Description of problem:

Trying to deploy a maven artifact with Fedora provided maven to nexus fails with a 401, although login credentials match. Mvn deploy process works with same maven version (3.0.5) downloaded from Apache or latest 3.1.1 from Apache. It looks like this error is still in the package: http://jira.codehaus.org/browse/MNG-3953 & http://jira.codehaus.org/browse/MNG-4469

Further evidence to proof that the upload is tried to be done without credentials is that the nexus log isn't showing anything for login attempts of the given user. 


Version-Release number of selected component (if applicable):
maven-3.0.5-3.fc19.noarch

How reproducible:

execute mvn deploy for maven project hosted on secured nexus, with authentication credentials provided in settings.xml

Steps to Reproduce:
1. Add authentication credentials to ~/.m2/settings.xml file
2. change into mvn project hosted on secured nexus
3. run mvn deploy

Actual results:
Deploy fails with 401 error

Expected results:
Deploy succeeds and maven artifacts are available.


Additional info:
Comment 1 Mikolaj Izdebski 2014-01-28 09:31:28 UTC 
This looks like a syntax error in settings file at /etc/maven/settings.xml. Can you check if removing this file and reinstalling maven helps?
Comment 2 Fedora Admin XMLRPC Client 2014-04-24 12:46:54 UTC 
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.
Comment 3 Mikolaj Izdebski 2014-05-12 05:02:46 UTC 
Authentication works for me.

Closing - there is insufficient information to reproduce the bug and the reporter didn't respond.  Feel free to reopen if there is a working reproducer available.
Comment 4 Ryan May 2014-08-12 18:58:34 UTC 
I'm having the same problem here: I get a 401 using the stock pom.xml and appropriate settings.xml and settings-security.xml. I can make it work by adding the following section to our top-level pom.xml (in the build section):

+    <extensions>
+           <extension>
+                   <groupId>org.apache.maven.wagon</groupId>
+                   <artifactId>wagon-http-lightweight</artifactId>
+                   <version>1.0</version>
+           </extension>
+    </extensions>

This was suggested here: https://jira.codehaus.org/browse/MNG-5525

I have not tried installing my own copy of Maven.