You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Benjamin Bentmann (JIRA)" <ji...@codehaus.org> on 2010/02/15 00:30:55 UTC

[jira] Commented: (MNG-4561) [regression] network settings are not applied to repositories from plugin dependencies

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

Benjamin Bentmann commented on MNG-4561:
----------------------------------------

Completed fix in [r909934|http://svn.apache.org/viewvc?view=revision&revision=909934].

The particular project mentioned here, nexus-archetype-plugin, suffered actually from two issues. The first issue was a straight forward bug where the proxy settings were not passed to the wagon. The second issue was that an old version of the HTTP wagon was being used which completey ignored proxy settings (WAGON-236). This old wagon version was pulled in via transitive dependencies of a build extension and basically duplicates MNG-4528.

> [regression] network settings are not applied to repositories from plugin dependencies
> --------------------------------------------------------------------------------------
>
>                 Key: MNG-4561
>                 URL: http://jira.codehaus.org/browse/MNG-4561
>             Project: Maven 2 & 3
>          Issue Type: Bug
>    Affects Versions: 3.0-alpha-6
>         Environment: Apache Maven 3.0-alpha-6 (r896384; 2010-01-06 11:00:46+0000)
> Java version: 1.6.0_16
> Java home: C:\Java\jdk1.6.0_16\jre
> Default locale: en_GB, platform encoding: Cp1252
> OS name: "windows xp" version: "5.1" arch: "x86" Family: "windows"
>            Reporter: James Nord
>            Assignee: Benjamin Bentmann
>             Fix For: 3.0-alpha-7
>
>
> See also MNG-4413, MNG-4489
> For some artifacts Maven ignores the proxy defined in the per user settings.xml and tries to connect directly which results in a connection timeout.
> I will attempt to create a simplified test case but meanwhile.
> 1) install a web proxy
> 2) install a nexus repo manager
> 3) configure your machine so it can not see the repo manager.
> 4) add central and sonatype forge to the repo manager and configre repo manager and settings.xml for proxy and mirror.
> 5) delete local repository
> 6) checkout http://svn.sonatype.org/nexus-plugins/trunk/nexus-archetype-plugin/
> 7) mvn package.
> The build will fail.
> delete the metadata for the associated failed files in the local repo
> run mvn -e package
> in another shell run netstat -an
> observe that the machine is trying to connect to repository.sonatype.org (63.246.20.88:80)
> observe that the stack traces the socket is a plain socket and it is a plain connect not a proxy connect.

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