Use ivy cachepath and cachefileset instead of ivy retrieve
----------------------------------------------------------
Key: LUCENE-3943
URL: https://issues.apache.org/jira/browse/LUCENE-3943
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:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
