[
http://jira.codehaus.org/browse/MRM-1413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=232943#action_232943
]
Elie Delorme commented on MRM-1413:
-----------------------------------
I was able to make the proxy work for ssl repos by adding
-Dhttps.proxyHost=my_proxy_host and -Dhttps.proxyPort=my_proxy_port to the
wrapper.conf file.
It works, but I consider this a workaround.
> network-proxy configuration doesn't seen to work
> ------------------------------------------------
>
> Key: MRM-1413
> URL: http://jira.codehaus.org/browse/MRM-1413
> Project: Archiva
> Issue Type: Bug
> Affects Versions: 1.3
> Reporter: Elie Delorme
> Attachments: archiva.xml
>
>
> Our machine doesn't even have a public ip, so all outbound connections have
> to go through an http proxy.
> 1. Added a remote repository with url
> "https://maven.atlassian.com/repository/public";
> 2. Added a network proxy called "adenyo-proxy"
> 3. Added a proxy-connector that uses both
> archiva.log:
> {noformat}
> 2010-07-30 12:09:15,162 [btpool0-12] WARN
> org.apache.maven.archiva.proxy.DefaultRepositoryProxyConnectors - Transfer
> error from repository "atlassian" for artifact
> org.apache.maven.plugins:maven-war-plugin:2.1-alpha-2::pom, continuing to
> next repository. Error message: Download failure on resource
> [https://maven.atlassian.com/repository/public/org/apache/maven/plugins/maven-war-plugin/2.1-alpha-2/maven-war-plugin-2.1-alpha-2.pom]:Error
> transferring file: Connection refused (cause: java.net.ConnectException:
> Connection refused)
> {noformat}
> Also, clicking on the settings link below a proxy connector and on the "Edit
> Network Proxy" link leads to an unconfigured proxy.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
