maven.repo.remote=http://www.apache.org/dist/java-repository/,http://www.ibiblio.org
Bretts correct that in this case the requests should fall over to ibibilio. It would be wise that Projects probably shouldn't be hardcoding the java-repository here. They should leave assigning this param upto the release manager for the project and use the default for all their development.
There is another case:
maven.repo.central.directory=/www/www.apache.org/dist/java-repository
this is actually bad as well, because the developers cutting interim builds will deploy them accidentally into the java-repository. I feel that this should be avoided as well by everyone but the release manager.
-Mark
Henk P. Penning wrote:
On Tue, 11 Jan 2005, Mark R. Diggory wrote:
Date: Tue, 11 Jan 2005 19:31:22 -0500 From: Mark R. Diggory <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Subject: Re: Where to publish Xalan code on http://www.apache.org/dist (fwd)
[ I wrote : ]
Remove ?
[ Mark : ]
I've been planning to, I'm just concerned of the impact, I'm trying to be thorough and verify it will not cause others major problems when I remove them.
[ but Brett wrote somewhere else : ]
Nobody is building against java-repository, they are using ibiblio, so there is no harm in cleaning these up AFAICT.
Mark, what kind of problems could result in removing things ?
According to Brett we could remove the entire repository, and nobody's build would fail (not that I'm suggesting that :-).
Are there other worries ?
HPP
---------------------------------------------------------------- _ Henk P. Penning, Computer Systems Group R Uithof CGN-A232 _/ \_ Dept of Computer Science, Utrecht University T +31 30 253 4106 / \_/ \ Padualaan 14, 3584CH Utrecht, the Netherlands F +31 30 251 3791 \_/ \_/ http://www.cs.uu.nl/staff/henkp.html M [EMAIL PROTECTED] \_/
-- Mark Diggory Open Source Software Developer Apache Jakarta Project http://jakarta.apache.org
