[ 
http://jira.codehaus.org/browse/MNG-4211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=209532#action_209532
 ] 

Bernhard Dangl commented on MNG-4211:
-------------------------------------

I'm rather new to maven but have found the following problem working with a 
proxy:

I use Maven 2.2.1 with Java 1.6.0_16.

I had to reach SSL-repositories as well as nonSSL-repositories via proxy. So I 
added the following lines to the settings.xml-file:

{code}
  <proxies>
    <proxy>
      <active>true</active>
      <protocol>http</protocol>
      <host>proxy.mycompany.com</host>
      <port>8080</port>
      <nonProxyHosts></nonProxyHosts>
    </proxy>
    <proxy>
      <active>true</active>
      <protocol>https</protocol>
      <host>proxy.mycompany.com</host>
      <port>8080</port>
      <nonProxyHosts></nonProxyHosts>
    </proxy>
  </proxies>
{code}

But maven fails to connect to either http- or https-repositories. This depends 
on the proxy setting mentioned first in the settings.xml.

Found the following solution:

I set the environment variable MAVEN_OPTS:
{code}
MAVEN_OPTS="-Dhttp.proxyHost=proxy.mycompany.com -Dhttp.proxyPort=8080 
-Dhttps.proxyHost=proxy.mycompany.com -Dhttps.proxyPort=8080 
-Dmaven.wagon.provider.http=httpclient -Dmaven.wagon.provider.https=lightweight"
{code}

With this settings maven works fine. So I had to specify different 
wagon-providers for the two protocolls to get it work.




> [regression] proxy access broken between maven version 2.0.10 and 2.1. 
> Probably due to addition of  wagon 1.0-beta-4+
> ---------------------------------------------------------------------------------------------------------------------
>
>                 Key: MNG-4211
>                 URL: http://jira.codehaus.org/browse/MNG-4211
>             Project: Maven 2 & 3
>          Issue Type: Bug
>          Components: Artifacts and Repositories
>    Affects Versions: 2.1.0, 2.2.0
>         Environment: WinXP SP2
>            Reporter: Robert Glover Jr
>            Priority: Blocker
>             Fix For: 2.2.2
>
>         Attachments: jira_files_4_total.zip
>
>
>   At a large company, maven become impossible to use via proxy when maven 
> upgraded from 1.0.10 to 2.1.  maven has always worked fine via proxy in 2.0.9 
> and continues to work fine.  however maven via proxy always fails in version 
> 2.1.0 and higher.  
>   Attached is a  zip file containing   1) log of GMAIL chat between the 
> creater of this JIRA and a maven developer.  2) two console outputs of 
> running maven 2.2. RC3 showing the proxy failure messages.  3) setting.xml 
> (with comments stripped out)

-- 
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

        

Reply via email to