[jira] Commented: (MNG-4354) DefaultArtifactResolver has problems when used with multiple repos

["Nicolas Dumoulin (JIRA)" <ji...@codehaus.org>]

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

Nicolas Dumoulin commented on MNG-4354:
---------------------------------------

I can confirm this annoying bug. For instance, our fix is to use our proxy as a mirro of the central repo.

> DefaultArtifactResolver has problems when used with multiple repos
> ------------------------------------------------------------------
>
>                 Key: MNG-4354
>                 URL: http://jira.codehaus.org/browse/MNG-4354
>             Project: Maven 2
>          Issue Type: Bug
>          Components: Bootstrap & Build
>    Affects Versions: 2.2.1
>         Environment: N/A
>            Reporter: Hasan Ceylan
>            Priority: Blocker
>         Attachments: maven.patch
>
>
> DefaultArtifactResolver attaches the repositories to artifacts (AFAIK) to optimize the repo look ups.
> Here I have a case
> 1) An artifact dependens on org.eclipse.equniox:app:1.2.0
> 2) org.eclipse.equinox:app depends on org.eclipse.equinox:registry:[3.4.0,4.0.0)
> 3) Both central repo and custom corporate repo has org.eclipse.equinox:registry
> 4) central repo has outdated versions
>      3.2.1-R32x_v20060814
>      3.3.0-v20070522
> 5) DefaultArtifactResolver for optimization attaches central repo (last one wins) 
> 6) Central repo neither satisfies the version range nor - even if it did - has the latest version
> 7) dependency is not satisfied
> 8) Build halts
> Attached patch is a dirty hack to disable signle repo downloand and checks all the repositories.

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