Hi Emerson, The behaviour of the virtual repositories used to be that once the artifact is found in any of the repositories, the other repositories would no longer be checked. It was changed to check all the repositories to handle cases such as range versions in Maven. Please see the following thread for more details:
http://www.nabble.com/wrong-metadatas-td18360791.html Hmm, maybe we could have this one configurable for the virtual repos (user can set whether to short-circuit download to the repo or not). Thanks, Deng On Sat, Nov 1, 2008 at 2:19 AM, emerson cargnin <[EMAIL PROTECTED]>wrote: > Could someone just tell me if that's the way it's suppose to work? > > 2008/10/30 emerson cargnin <[EMAIL PROTECTED]>: > > Any idea how I can configure arquiva so that after the first > > repository (following the order) would return the jar archiva wouldn't > > request the same jar to other repositories down the list? > > > > regards > > Emerson > > > > 2008/10/28 deckrider <[EMAIL PROTECTED]>: > >> I had also assumed that the order within the repository group meant > >> something in this regard. > >> > >> On Mon, Oct 27, 2008 at 7:42 AM, emerson cargnin > >> <[EMAIL PROTECTED]> wrote: > >>> Hi > >>> > >>> I set up a repository group that centralises all our repositories. > >>> > >>> This includes: > >>> - internal: jars that are not public available and internal libraries > >>> - public: this repo proxies all jars available in maven repository > >>> (Proxy Connector to http://repo1.maven.org/maven2) > >>> - internal legacy: old m1 repository that has both non public and > >>> public jars. (Proxy Connector to our old ftp m1 repo) > >>> > >>> The way I created the archiva setup, my repository group should get > >>> the public jars into the "public" archiva repository (from > >>> http://repo1.maven.org/maven2). > >>> I believe the order of the repo in the group (virtual repo) means that > >>> the first repos listed there are searched first right? > >>> > >>> I wanted to use this behaviour to filter out unnecessary public jars > >>> that previously we kept on our m1 legacy repository. After a while I > >>> could go to the archiva legacy repo and see which jars are efectivelly > >>> need to be moved into the archiva "internal" repo. > >>> > >>> The problem is that the way the repository group is working, once I > >>> try to download commons-lang-2.4.jar, for example, archiva connects > >>> to both repositories, and proxy it locally, instead of looking in the > >>> public one first, and as it finds the jar there, there is no need to > >>> to get from the legacy internal m1. > >>> > >>> Is this the way the repository groups should work? Is there a way to > >>> enforce that once a jar has been found in one of the repositories in > >>> the group, the other ones wouldn't be searched? > >>> > >>> Regards > >>> > >>> Emerson > >>> > >> > >> > >> > >> -- > >> ASCII ribbon campaign: > >> () against HTML email > >> /\ against Microsoft attachments > >> Information: http://www.expita.com/nomime.html > >> > > >
