one low-tech, pre-built way to do it would be to use wget (linux utility) or something like that, and point it at http://www.ibiblio.org/maven. That should simply do a traversal of the webserver's directory and retrieve the artifacts stored there...
You probably don't need all of it, though, so I'd probably run a build of all your projects in some open environment (allows you to d/l), and copy the resulting cached local repo to your internal web/file server. Then, everyone's ~/build.properties file should be changed to have something like: maven.repo.remote=http://my.internal.server/maven or, using a fileserver: maven.repo.local=/path/to/maven/libs I'd probably choose the first option, since it most closely reflects maven's "natural" environment, and therefore is less likely to experience funny bugs. hope this rambling helps... -john On Fri, 2004-08-06 at 15:27, Kim Goings wrote: > I'm currently working at a site where developers are not allowed to > download anything to their workstations (directly or indirectly) > without permission. In order to get approval to use Maven, I need to > build a local copy of the ibiblio repository. > > Has anyone else had to do this? Have any automation you'd be willing > to share? I have a couple approaches for automating it, but I'd be > ecstatic if someone else had already written something I could reuse. > > Thanks, > Kim > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] -- John Casey [EMAIL PROTECTED] CommonJava Open Components Project http://www.commonjava.org --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
