On Fri, Oct 16, 2009 at 11:15 AM, Rob Slifka <[email protected]> wrote: > I'm working on wrapping my head around setting up an internal "blessed" > repository and being assured that Maven will fail when a dependency is not > found there. > > (1) Clear my local repo. > (2) Run Maven through our lifecycle (clean, compile, package, test, etc.). > (3) Take the contents of my now-populated local repo and copy them up to a > shared location.
The local repository format is not the same as the remote repo format. The metadata is different, which is probably why you're having trouble with plugins. You've already heard why a repo manager is a good thing. :) But to start out, you just use a directory exposed through an existing web server or a network share that's visible to everyone. In settings.xml, (or pom.xml) redefine the repository with <id>central</id> to some other url. You can use 'mvn deploy:deploy-file ...' to deploy artifacts to your remote repo with the correct format and metadata. -- Wendy --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
