[jira] [Commented] (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:comment-tabpanel=17297240#comment-17297240
]
Michael Osipov commented on MNG-5828:
-
Are you joking? Look at the stack trace, fix your truststore setup. It is
completely unrelated to this.
> 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
> Labels: close-pending
> Attachments: failed-dbg.log, failed.log, hauser_install_verbose.txt,
> 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
(v8.3.4#803005)
[jira] [Commented] (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:comment-tabpanel=17297210#comment-17297210
]
Daniel Hauser commented on MNG-5828:
[~michael-o], I've uploaded the verbose output for a install command, I hope
that's what you mean: [^hauser_install_verbose.txt]
> 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
> Labels: close-pending
> Attachments: failed-dbg.log, failed.log, hauser_install_verbose.txt,
> 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
(v8.3.4#803005)
[jira] [Commented] (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:comment-tabpanel=17296543#comment-17296543
]
Michael Osipov commented on MNG-5828:
-
[~DanHau], please provide debug output and out settings configuration and I
will reassess.
> 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
> 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
> (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
(v8.3.4#803005)
[jira] [Commented] (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:comment-tabpanel=17289855#comment-17289855
]
Daniel Hauser commented on MNG-5828:
We're having the same exact problem with Maven 3.6.3, exactly as [~jelion]
described.
> 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
> 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
> (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
(v8.3.4#803005)
[jira] [Commented] (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:comment-tabpanel=16390345#comment-16390345
]
Michael Osipov commented on MNG-5828:
-
Is this one still valid?
> 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
> 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
> (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
(v7.6.3#76005)
[jira] [Commented] (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:comment-tabpanelfocusedCommentId=14565829#comment-14565829
]
John Elion commented on MNG-5828:
-
I have successfully worked around the issue by setting up a local Nexus server
which forwards through our firewall to external repositories; such that all of
Maven's requests are routed to a local mirror. Through Nexus , Maven seems
to have successfully retrieved artifacts that had failed when Maven reached out
directly to the internet through the firewall proxy.
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)
