You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "John Elion (JIRA)" <ji...@apache.org> on 2015/05/22 17:58:17 UTC

[jira] [Updated] (MNG-5828) Artifact download loses proxy username during transfer, failing download

     [ https://issues.apache.org/jira/browse/MNG-5828?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

John Elion updated MNG-5828:
----------------------------
    Attachment: settings.xml
                pom.xml
                failed-dbg.log
                failed.log

These files lived in c:\jdev\mavenissue\proj; there are references to c:\jdev\mavenissue in both settings.xml and pom.xml that are easily changed if the project parent folder is relocated.  The proxy configuration obviously also would need to be tweaked for the local environment.

The command to reproduce was simply 'mvn -s settings.xml site' from the folder containing pom.xml; the local repository was created in ..\repos (so it could be quickly deleted and retried)

The host system is Windows 7 Enterprise SP1 64-bit; Maven version was 3.3.3, Java version was 7u55 x64.  The proxy host is a McAfee Web Gateway

> Artifact download loses proxy username during transfer, failing download
> ------------------------------------------------------------------------
>
>                 Key: MNG-5828
>                 URL: https://issues.apache.org/jira/browse/MNG-5828
>             Project: Maven
>          Issue Type: Bug
>          Components: Artifacts and Repositories
>    Affects Versions: 3.3.3
>         Environment: Windows 7 Enterprise SP1 x64
>            Reporter: John Elion
>            Priority: Minor
>         Attachments: failed-dbg.log, failed.log, pom.xml, settings.xml
>
>
> Executing 'mvn site' causes Maven to successfully download most artifacts, but several failures are reported with the message 
> [WARNING] Could not transfer metadata org.codehaus.mojo:findbugs-maven-plugin/maven-metadata.xml from/to central (https://repo.maven.apache.org/maven2): Error transferring file: Unable to tunnel through proxy. Proxy returns "HTTP/1.1 407 authenticationrequired" from https://repo.maven.apache.org/maven2/org/codehaus/mojo/findbugs-maven-plugin/maven-metadata.xml with proxyInfo ProxyInfo{host='mamwg.gdc4s.com', userName='null', port=8080, type='https', nonProxyHosts='null'}
> The proxy configuration does specify a username, and a "mvn -X" log shows Maven to be aware of the username a few lines earlier.
> [DEBUG] Using connector BasicRepositoryConnector with priority 0.0 for https://repo.maven.apache.org/maven2 via mamwg.gdc4s.com:8080 with username=p58042, password=***
> I don't see a way to attach, but if I can do so after saving I will attach a fairly simple pom file, settings.xml (stripped of passwords), and plain and debug log files that will reproduce the error with the commands 'mvn -s settings.xml site' and 'mvn -X -s settings.xml site'.
> I have listed this as "minor" because my end build results thus far have been successful and the components which have failed to download have apparently not impacted my building or testing - in some cases it appears the component is already downloaded to my local repository; however, there are hundreds of these warnings in my build logs.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)