On Mon, Jan 26, 2009 at 5:47 PM, Marc Canaleta <[email protected]> wrote:
> Hi, > > I'm using apache archiva 1.1.3 as internal repository and as external > repositories proxy (central, codehaus, ...). What is the correct > approach? > - A single repository (internal) as repository for internal projects > and external repositories proxy. > - One internal repository for internal projects and one repository as > proxy for all extenral repositories. > - One internal repository for internal projects and one repository for > each external repository proxy (central, codehaus, ...) I say go with the 2nd option :) There isn't a problem with the third option but that could mean lots of repositories/mirrors to configure in your settings.xml. The first option doesn't give you much flexibility to control access to the internally released artifacts and the proxied artifacts since Archiva's access control is at the repository level. > Is there any problem in joining releases and snapshots repository? Not exactly a problem, but it's good practice to keep snapshots and releases in separate repositories. Releases are stable and are usually published for public consumption while snapshots are use-at-your-own-risk artifacts, so it doesn't seem right that there are unstable artifacts (snapshots) available in a repository which is for public consumption.. :) > > > Thank you > HTH, Deng -- Maria Odea Ching Software Engineer | Exist Global | 687-4091 | Skype: maria.odea.ching | www.exist.com | Innovation Delivered
