2008/2/5, Brett Porter <[EMAIL PROTECTED]>: > > On 05/02/2008, at 8:50 PM, Tomasz Pik wrote: > > > On Feb 5, 2008 9:03 AM, Raphaël Piéroni <[EMAIL PROTECTED]> > > wrote: > >> The main list is the internal catalog. > >> It is also possible to define a specific catalog > >> by -DarchetypeCatalog=http://repo.company.com/maven2 the catalog > >> is an xml file located at the root and called archetype-catalog.xml. > > Should archetype catalog reside at the group level, to be consistent > with the plugin metadata?
Catalog is intended to be repository wide > > >> > > > > Perhaps it would be a good addition to archiva: creating such catalog > > on the fly using database of artifacts already handled by archiva. > > It would be a kind of chicken-egg thing (given archetype is not on > > a list because nobody asked for it and nobody asked for it because > > it's not on a list) but this also may be handled in 'distributed way' > > (while asking for catalog archiva will go through proxied > > repositories, > > asking for their catalogs and result will be a sum of all > > repositories). > > Yep - this should be no problem - we essentially do the same thing for > the metadata already, so the addition of a consumer could do this. It > would also need to learn how to merge the metadata so that it can be > proxied properly but everything else is in place. Would you like to > file a request in JIRA? > > Cheers, > Brett > >
