On 21/10/2010, at 8:34 PM, Gretar Arnason wrote: > Hi, I was wondering if it is possible to configure a repository in such way > that if the artifact is found in it then other repositories are not searched?
This is how repositories behave now. > > The specific problem I have can be described like this: > > I've got 3 repositories > > mavenRepo name="localRepo" urls:"file://....." > mavenRepo name="remoteRepo1" urls:"http://...."; > mavenRepo name="remoteRepo2" urls:"http://...."; > > What I would like to be able to do is to first search localRepo and if > artifact is found there - pick the one with highest version from there. > I very selectively put and remove artifacts in localRepo (local builds of > modules put their artifacts there), i.e. it has a very dynamic content. > If not found in localRepo then search remoteRepo1 and remoteRepo2 just the > normal way. > > Is this possible in some way or do I need to extend some classes to get this > behavior. > > I would also welcome other suggestions on achieving the same effect. > Could you explain what you want to achieve a bit more? ie, why do you want to look in localRepo first then the remote repos? -- Adam Murdoch Gradle Developer http://www.gradle.org CTO, Gradle Inc. - Gradle Training, Support, Consulting http://www.gradle.biz
