[ http://jira.codehaus.org/browse/MNG-145?page=all ]
Brett Porter closed MNG-145:
----------------------------
Resolution: Fixed
went for the settings.xml solution here for now. Reading a list of mirrors from
the repository itself can be a future step.
> built in notion of a mirror repository
> --------------------------------------
>
> Key: MNG-145
> URL: http://jira.codehaus.org/browse/MNG-145
> Project: m2
> Type: Improvement
> Reporter: Brett Porter
> Assignee: Brett Porter
> Fix For: 2.0-alpha-2
>
>
> this probably relates to repository work as much as Maven work.
> Currently, if users wish to use a mirror of ibiblio, they specify that as an
> alternative remote repository. In m1, this causes a problem because if you
> add a new repository not equivalent to that in your project, it is not in the
> build.properties.
> In m2, they are all added to the list, so the mirror will be used first, but
> the others may also be checked. This is better, but still requires the user
> specify it in their configuration and it may be used on projects it is never
> needed for.
> It would be good if we could have a repository descriptor at the base of the
> repository that lists mirrors. On first use of the repository, the user could
> be prompted to select any mirrors they'd like to use, and it can be saved in
> their configuration for that repository ID.
> That way any project listing ibiblio as a repository could actually use, say,
> planetmirror instead (and fall back to ibiblio last).
--
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
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
