archiva-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Maria Odea Ching <och...@apache.org>
Subject Re: Repositories organization
Date Mon, 26 Jan 2009 14:46:31 GMT
On Mon, Jan 26, 2009 at 6:37 PM, Marc Canaleta <mcanaleta@gmail.com> wrote:

> Thanks for the explanation.


Np :)


>
> I was using the 2nd option, but it seemed that the performance became
> poor as the repository grew up, so I changed to the 3rd, but the
> problem was not solved.


Hmm, how did you configure your proxy connectors?
There are options whether to always download the artifacts from the remote
repository or do this only once or never fore releases and snapshots..


> It looks like an index related problem. Keeping the "Index Directory"
> field empty meens the repository won't be indexed, or it will use a
> default value?


It would use a default value which is [REPO_LOCATION]/.index/
If you'd like to disable the indexing, just disable the index-content
consumer in the Repository Scanning page and the
index-artifact, index-public-methods and index-archiva-toc consumers in the
Database Scanning page.


Thanks,
Deng


>
> Thank you
>
> 2009/1/26 Maria Odea Ching <oching@apache.org>:
> > On Mon, Jan 26, 2009 at 5:47 PM, Marc Canaleta <mcanaleta@gmail.com>
> 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
> >
>



-- 
Maria Odea Ching
Software Engineer | Exist Global | 687-4091 | Skype: maria.odea.ching |
www.exist.com | Innovation Delivered

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message