First off, thanks to Matt and the admins for the workaround! On Tue, Jun 06, 2006 at 11:36:32PM -0400, Matt Hogstrom wrote: > In general the problem is really people that are getting involved with > Geronimo for the first time as they start out with an empty repo. The > developers and others on the project generally have an up to date repo and > work offline to get a build to go faster.
It's worse than that. The problem is that anytime one of the dependencies changes you need to do an online build to get it, and that online build makes dozens and dozens of requests to various remote repositories for artifacts that already exist locally. > Noel J. Bergman wrote: > >Joshua Slive wrote: > > > >>So you not only have your build process tied to apache infrastructure > >>in a non-scalable way > > > >Is this the issue with Maven not handling redirects, or something else? Among other things, it's an issue with Maven making requests to remote servers for artifacts that were built locally, which is very wasteful. Sure, there's the "-o" flag but you can't run "-o" all of the time.
