You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Dennis Homann (JIRA)" <ji...@codehaus.org> on 2011/07/26 18:31:42 UTC
[jira] Commented: (MNG-4354) DefaultArtifactResolver has problems
when used with multiple repos
[ https://jira.codehaus.org/browse/MNG-4354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=274280#comment-274280 ]
Dennis Homann commented on MNG-4354:
------------------------------------
I just stumbled upon a problem which sounds related:
* an artifact was resolved from a remote mirror and placed in the local repository, along with a file _maven.repositories which points to the ID of mirror where the artifact was resolved from
* when I disconnect from the network, Maven will try to resolve the artifact from remote repositories although it is present locally, and the build will fail
* when I disconnect from the network AND run with -o, Maven will fail with "The repository system is offline but the artifact ... is not available in the local repository."
* when I delete the _maven.repositories file for the artifact in question, it will get resolved locally and the build will fail for the next dependency as described above
> DefaultArtifactResolver has problems when used with multiple repos
> ------------------------------------------------------------------
>
> Key: MNG-4354
> URL: https://jira.codehaus.org/browse/MNG-4354
> Project: Maven 2 & 3
> Issue Type: Bug
> Components: Bootstrap & Build
> Affects Versions: 2.2.1
> Environment: N/A
> Reporter: Hasan Ceylan
> Priority: Blocker
> Fix For: Issues to be reviewed for 3.x
>
> 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira