Why not use a corporate repository manager like Nexus or Artifactory? All users would then configure their Maven to use that as the remote repo for all artifacts. This will give you a central point where you manage all artifacts, including both external and internal ones. His instance would then proxy any remote repos on Internet (if you allow it too).
Any other solution is a hack. /Anders On Tue, Dec 15, 2009 at 14:19, Gajo Csaba <[email protected]> wrote: > This seems to be almost perfect except it requires a project to exist. But > I'll use it if there's nothing else :) > > Thanks, Csaba > > > > Jesse Farinacci wrote: > >> Hi Gajo, >> >> 2009/12/15 Gajo Csaba <[email protected]>: >> >> >>> Is there some cleaner way to do this? I know exactly which dependencies >>> are >>> needed (it's a large list), so is there some maven command to not build >>> anything, just download these dependencies into the local .m2 directory? >>> >>> >>> >> >> Check out the maven-dependency-plugin:go-offline goal: >> >> >> http://maven.apache.org/plugins/maven-dependency-plugin/go-offline-mojo.html >> >> -Jesse Farinacci >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> >> >> > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
