It seemed easier to just add a proxy connector to another 3rd party repository so I don't have to change the settings.xml files for all my users. I was just unsure if/how Archiva behaved when mixing external release and snapshot repo's. Sounds like it isn't a big deal.
Thanks for the info on the virtual repositories. I saw the "groups" feature in 1.4-M2, but had problems with it so I"m back to 1.3.5 and didn't realize it could do that....so much to learn :). On Tue, Apr 17, 2012 at 9:24 AM, Deng Ching <[email protected]> wrote: > On Tue, Apr 17, 2012 at 2:57 AM, Jeff <[email protected]> wrote: > > > I have a "snapshot" repository currently used for internal snapshots as > > well as an "Internal" repository to contain both internal release > artifacts > > as well as caching remote repository artifacts via proxy connectors. > > > > When I set up the "Internal" repository, I disabled the "Snapshots > > Included" setting. > > > > If I want to setup an external 3rd party SNAPSHOT repository to get > access > > to a release candidate build from an external repo, do I connect that > > proxy > > to my "snapshots" repository or connect it to "Internal" repository? > > > Hmm, I'm a bit lost here.. why not just create the 3rd party SNAPSHOT repo > in the same Archiva instance and have it proxy the external repo where the > release candidate build is? > > > > If > > connected to "Internal", do I enable or disable the "Snapshots Included" > > setting? > > > > It isn't clear to me if the "Snapshots Included" setting only applies to > > publishing builds or how it resolves artifact requests.... > > > > It's more for the benefit of publishing builds and has nothing to do with > resolving artifact requests. IIRC, that setting is mainly used as a quick > identifier whether the repository contains snapshots and/or releases for > administration purposes and for repo purge. > > I would suggest that you keep your snapshot artifacts from released ones > then also keep your internal releases and internal snapshots build separate > from your proxy repositories. This would give you better control over who > can access which artifacts. You can create a repository group for all your > repositories (internal, snapshots, internal-releases, etc.) so you can just > point to one url to access all the artifacts. Check out the link below for > more details on this. > > http://archiva.apache.org/docs/1.3.5/userguide/virtual-repositories.html > > Thanks, > Deng > -- Jeff Vincent [email protected] See my LinkedIn profile at: http://www.linkedin.com/in/rjeffreyvincent I ♥ DropBox <http://db.tt/9O6LfBX> !!
