[ 
https://jira.codehaus.org/browse/MANTTASKS-175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Osipov closed MANTTASKS-175.
------------------------------------

    Resolution: Won't Fix

Please refer to 
https://cwiki.apache.org/confluence/display/MAVEN/The+Great+JIRA+Cleanup+of+2014
 if you're wondering why this issue was closed out.

> Dependencies ignoring user defined repo location and reverting to central
> -------------------------------------------------------------------------
>
>                 Key: MANTTASKS-175
>                 URL: https://jira.codehaus.org/browse/MANTTASKS-175
>             Project: Maven Ant Tasks
>          Issue Type: Bug
>          Components: dependencies task
>    Affects Versions: 2.1.0
>         Environment: Windows XP
>            Reporter: Paul WIlliams
>         Attachments: wagonManagerInit.patch
>
>
> I have a very simple dependencies declaration:
> {code:xml}<artifact:dependencies filesetId="dependency.fileset" 
> settingsFile="${app.mavenSettings}">
>     <dependency groupId="com.mycompany.infrastructure" artifactId="artifact" 
> version="2.0.0"/>
> </artifact:dependencies>{code}
> I have 2 mirrors set up:
> {code:xml}<mirrors>
>       <mirror>
>               <id>all_mirror</id>
>               <name>Nexus All</name>
>               <url>http://maven-proxy.mycompany.com/content/groups/all</url>
>               <mirrorOf>*,!central</mirrorOf>
>       </mirror>
>       <mirror>
>               <id>central_mirror</id>
>               <name>Nexus Releases</name>
>               
> <url>http://maven-proxy.mycompany.com/content/groups/public</url>
>               <mirrorOf>central</mirrorOf>
>       </mirror>
> </mirrors>{code}
> When I instruct Maven to retreive the dependency it gets the pom file 
> correctly, which contains a 2nd dependency, which is retrieved. These are 
> both retrieved from the correct repo. But the 2nd pom then defines another 
> dependency. But this 3rd dependency is searched for at central, where it 
> doesnt exist (all artifacts are internal libraries).
> {noformat}
> Downloading: com/mycompany/myartifact1/version1/artifact1-version1.pom from 
> repository central_mirror at http://mycompany.com/content/groups/public
> Transferring 4K from central_mirror
> Downloading: com/mycompany/myartifact2/version2/artifact2-version2.pom from 
> repository central_mirror at http://mycompany.com/content/groups/public
> Transferring 24K from central_mirror
> Downloading: com/mycompany/myartifact3/version3/artifact3-version3.pom from 
> repository central at http://repo1.maven.org/maven2
> Error transferring file: Connection timed out: connect
> {noformat}
> So the first 2 are resolved and d/loaded fine, but the 3rd suddenly reverts 
> to looking in central, when it is present and correct in the central_mirror 
> repo.



--
This message was sent by Atlassian JIRA
(v6.1.6#6162)

Reply via email to