maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Osipov (JIRA)" <>
Subject [jira] [Commented] (MNG-5828) Artifact download loses proxy username during transfer, failing download
Date Wed, 07 Mar 2018 22:24:00 GMT


Michael Osipov commented on MNG-5828:

Is this one still valid?

> Artifact download loses proxy username during transfer, failing download
> ------------------------------------------------------------------------
>                 Key: MNG-5828
>                 URL:
>             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
>              Labels: close-pending
>         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 ( Error transferring file: Unable to
tunnel through proxy. Proxy returns "HTTP/1.1 407 authenticationrequired" from
with proxyInfo ProxyInfo{host='', userName='null', port=8080, type='https',
> 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
via 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

View raw message