Uploaded image for project: 'Maven'
  1. Maven
  2. MNG-5828

Artifact download loses proxy username during transfer, failing download



    • Type: Bug
    • Status: Closed
    • Priority: Minor
    • Resolution: Not A Problem
    • Affects Version/s: 3.3.3
    • Fix Version/s: None
    • Labels:
    • Environment:
      Windows 7 Enterprise SP1 x64


      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.


        1. settings.xml
          1 kB
          John Elion
        2. pom.xml
          3 kB
          John Elion
        3. failed-dbg.log
          711 kB
          John Elion
        4. failed.log
          266 kB
          John Elion



            • Assignee:
              jelion John Elion
            • Votes:
              0 Vote for this issue
              3 Start watching this issue


              • Created: