Am 01.08.2011 22:09, schrieb Benson Margulies: > I have several alternative design ideas. > > 0) If you religiously use a repository manager and mirrorOf "*", you > can prevent this rogues from bothering you. Hi,
we do this and still have the need to use a settings.xml, for two reasons: - at work, different teams use different repository managers as mirror. On our CI server, we thus need to use our own settings.xml. - at home, I have a project which I want to build using both a local/private CI server and a "public" one, but they all use different repo managers as mirror *Nevertheless* I already do use project-specific settings.xml from SCM, in exactly this context. It's as easy as: - check in your settings.xml - run mvn -s settings.xml <goals> in checkout directory You could even split the settings.xml files into a different SCM repository and create one branch each for different environments, referring to the mirrors which should be active in this environment. Our CI server software can check out multiple SCM roots per build configuration, so we could checkout "settings.xml (internal) + main code base" on the internal CI server, plus "settings.xml (public) + main code base" on the public CI server. I don't strictly see the need to add auto-search functionality of settings.xml to Maven for this to work, the existing -s switch suffices at least for my use case. I can't see why this should not suffice for the use case of the OP. Best regards Ansgar --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
