maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Paul Benedict (JIRA)" <j...@codehaus.org>
Subject [jira] (MNG-4354) DefaultArtifactResolver has problems when used with multiple repos
Date Wed, 02 Jul 2014 13:44:27 GMT

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

Paul Benedict updated MNG-4354:
-------------------------------

    Fix Version/s:     (was: Issues to be reviewed for 3.x)

> DefaultArtifactResolver has problems when used with multiple repos
> ------------------------------------------------------------------
>
>                 Key: MNG-4354
>                 URL: https://jira.codehaus.org/browse/MNG-4354
>             Project: Maven
>          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 was sent by Atlassian JIRA
(v6.1.6#6162)

Mime
View raw message