On 07/01/2012, at 2:44 AM, Daz DeBoer <[email protected]> wrote:
> Hi Luke
>
> Thanks for pointing this out. Proved a little tricky to diagnose, as this
> problem doesn't exist in either M6 or HEAD.
>
> The problem is that we're not using our custom POM parsing code for local
> repositories: ivy default behaviour is to try to resolve javadoc and source
> jars for every module, and this lookup is not restricted to the same
> resolver. So not finding javadoc/source jars locally, ivy proceeds to search
> all available resolvers for these. This all happens down in
> dependency-resolver land, below our caching layer.
>
> This was fixed in a recent refactoring that consolidated our local and remote
> caches somewhat: they now share the same descriptor parsing infrastructure,
> including our custom no-source-or-javadoc-downloading pom parser.
Awesome work Daz.
> I'm sure people are using mavenLocal as a caching layer, and we should
> discourage this. There's not much point now that we can reuse artifacts from
> maven transparently.
I've seen a lot of projects using mavenLocal unnecessarily lately. I'm planning
on writing something up (for my blog) to explain why this is a bad idea, maybe
we can extract some user guide material from that.
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
