2009/4/17 Steve Appling <[email protected]> > > > Hans Dockter wrote: > >> >> On Apr 15, 2009, at 7:45 PM, Steve Appling wrote: >> >> I'm not sure if this is a gradle or ivy issue, but wanted to bring up a >>> problem I have seen since work is being done on the dependency layer. >>> >>> If I have two unrelated projects A and B that are both on the same >>> computer. >>> >>> A uses addMavenStyleRepo('myrepo', 'http://...') >>> B uses addMavenRepo() >>> >>> Both A and B have >>> dependencies { compile 'commons-digester:commons-digester:1.5' } >>> >>> If I build A first, gradle will resolve the dependency from myrepo and >>> cache the jar under >>> USER_HOME/.gradle/cache/commons-digester/commons-digester. The >>> ivydata-1.5.properties file in this directory contains: >>> ... >>> artifact.resolver=myrepo >>> ... >>> resolver=myrepo >>> ... >>> >>> When I try to build B, I will get the errors: >>> :: problems summary :: >>> :::: ERRORS >>> unknown resolver myrepo >>> >>> unknown resolver myrepo >>> >>> unknown resolver myrepo >>> >>> I have to manually delete the USER_HOME/.gradle/cache/ directory to be >>> able to build B. >>> >> >> I have filed a Jira to Ivy about this a while ago ( >> https://issues.apache.org/jira/browse/IVY-758). >> >> Did the build really fail for you? >> >> In my case I got the error message the first time I run the build with the >> new resolver (the build was successful). With the second run the message >> went away. >> >> Of course when you switch back and forth between those projects you will >> continuously encounter those messages, which is really annoying. You might >> comment/vote on the Ivy issue. >> >> - Hans >> >> > > It behaves as you describe. It didn't really fail, but it printed out > errors the first time you switched projects and it works with no message in > subsequent builds (until you switch projects again). I'll vote for this on > Ivy - thanks! > I've also voted for this ivy issue, really don't like the build noise ;)
> > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > >
