On Thu, May 29, 2008 at 12:44 PM, Dennis Lundberg <[EMAIL PROTECTED]> wrote:
> Hi Welcome :) > 1. Get the stuff from our file: repos into Archiva > Can we just tar/zip up the entire file repo and copy the whole thing over to > the data directory in Archiva? The location for each repo is configurable, so you don't necessarily have to move them. Once you decide where, configure each managed repo in Archiva. > 2. Have the configuration in the "best" place > > I read the previous thread "Choosing which repositories you install to" with > interest. Judging by that, we should remove the <repositories> configuration > from our parent POM and move it into each developers settings.xml, right? Consider creating a custom Maven distribution to use internally-- replace conf/settings.xml with one that contains your internal repository config. This also allows you to control (or at least influence) what version the developers are using, since you have the "official" one. If that doesn't suit, then ~/.m2/settings.xml is the next best option. > 4. Use Archiva as a proxy > Set up a mirror configuration in every developers settings.xml like this > > <mirror> > <id>company.com</id> > <name>Our Archiva Server</name> > <url>http://archiva.company.com/archiva</url> > <mirrorOf>*</mirrorOf> > </mirror> > > So that all downloads, both for company internal artifacts and for open > source artifacts available in the central repo, will be made through > Archiva. I've never seen a setup that has only *one* managed repository-- for a single mirror to work you'd have to have all your snapshots, releases, and third-party artifacts in a single repository. At least, you would until the 'virtual repository' feature is released, unless you're willing to try out a snapshot. I think I'd still group releases and snapshots separately, though I haven't experimented with that feature yet. -- Wendy
