On 24/03/2008, Jan Nielsen <[EMAIL PROTECTED]> wrote: > Sorry for the pedantic question, but is "archiva.default" a special > ID, or should this ID be changed to match the ID of the repository in > the Archiva "Managed Repositories" section that we want "*" to go to? > Or is it just specific to the <mirrors> elements? I suspect it's the > latter.
Correct, it's not special. > > But, in any case, for some reason when I try "mvn site" I get: I suspect this is MRM-734. > If I try to browse to my Archiva repository I'm prompted to do > BasicAuth; when I submit my archiva admin webapp credentials, I can > see that my repository does not contain this plugin, but the proxy > connector should pick that up, right? I don't know why I'm being > prompted for BasicAuth - I didn't configure it anywhere, and I can't > seem to turn it off, either. So, can I turn off BasicAuth? Is the > authentication the reason I can't resolve this plugin? Or do I need a > profile with pluginRepositories which identify this same repository as > my plugin repository? That might be an issue too. You can grant guest access to read the repository (instructions are contained on the web site). > (Side question: why do we even need to distinguish the plugin > repository from non-plugin repositories? Isn't it just a set of > artifacts which happen to b Maven plugins?) Yes, it is probably something that will be deprecated in future versions of Maven. - Brett -- Brett Porter Blog: http://blogs.exist.com/bporter/
