Hi, Our handling of mavenLocal() is pretty busted. There are numerous issues for this.
The most important is that fact that we don't treat mavenLocal() in that same way that m2 does; we stop resolution if we find any artifacts (including POMs) for a dependency in there. Recently I've had lots of people struggling with this because they have lots of POMs and no jars for artifacts in their maven local cache. I'm not sure what tooling exactly is populating the local m2 repo with just POMs, but it seems fairly common. The other big problem is that we install unique snapshots into the local cache, while mvn does not. Even in m3. Just wondering what our short - medium term plan on this is. Many people rely on mavenLocal() daily for sharing development snapshots, regardless of all the inherent problems with that concept. I can sense some pressure building around this, and it feels like something we should come up with a solution for some time soonish. -- Luke Daley Principal Engineer, Gradleware http://gradleware.com --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
