This seems a little too much magic to me - is there any use case for it outside of the integration tests? Would --ignore-mirrors or -- ignore-mirror-for ID be more appropriate? I've been using a replacement settings.xml file, but that blasts local repository setting and other mirrors.

- Brett

On 14/03/2008, at 9:25 AM, Brian E. Fox wrote:

Wiki:
http://docs.codehaus.org/display/MAVEN/Mirror+Settings+and+File+reposito
ries
Jira: http://jira.codehaus.org/browse/MNG-3461

-----Original Message-----
From: Brian E. Fox [mailto:[EMAIL PROTECTED]
Sent: Thursday, March 13, 2008 5:59 PM
To: Maven Developers List
Subject: [Proposal] mirror settings and file:// repositories

I ran into some issues recently with the IT tests. I use a mirrorof * to
redirect everything to a repo manager but this is also redirecting the
file based repositories. I can't think of any good reason this should
apply to anything other than remote repos. I have two proposals:



1. Change maven so that file based repos ignore all mirror settings

2.      Change maven so that file based repos ignore the wildcard but
will respond if the mirror specifically names it.



Like I said, I can't think of any reason why a mirror should override a
local repo so I suggest we go with #1. I'm targeting this change for
2.0.9.


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


--
Brett Porter
[EMAIL PROTECTED]
http://blogs.exist.com/bporter/


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to