lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael McCandless (Commented) (JIRA)" <>
Subject [jira] [Commented] (LUCENE-3943) Use ivy cachepath and cachefileset instead of ivy retrieve
Date Tue, 03 Apr 2012 10:56:23 GMT


Michael McCandless commented on LUCENE-3943:

Would this also mean ivy doesn't have to copy the JARs from its cache, into each checkout?
 So this will save disk space for devs w/ multiple checkouts...
> Use ivy cachepath and cachefileset instead of ivy retrieve
> ----------------------------------------------------------
>                 Key: LUCENE-3943
>                 URL:
>             Project: Lucene - Java
>          Issue Type: Improvement
>          Components: general/build
>            Reporter: Chris Male
> In LUCENE-3930 we moved to resolving all external dependencies using ivy:retrieve.  This
process places the dependencies into the lib/ folder of the respective modules which was ideal
since it replicated the existing build process and limited the number of changes to be made
to the build.
> However it can lead to multiple jars for the same dependency in the lib folder when the
dependency is upgraded, and just isn't the most efficient way to use Ivy.
> Uwe pointed out that we can remove the ivy:retrieve calls and make use of ivy:cachepath
and ivy:cachefileset to build our classpaths and packages respectively, which will go some
way to addressing these limitations

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message