[
https://issues.apache.org/jira/browse/LUCENE-3943?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13245613#comment-13245613
]
Hoss Man commented on LUCENE-3943:
----------------------------------
bq. In my opinion, the ideal situation would be that we pass these filesets
directly to the zip/tar/gz whatever in the binary release targets
the one catch that occurs to me is the solr example: start.jar, the libraries
jetty looks for, and the optional jar's solr load by path based on it's
configuration ... we just have to make sure "ant example" takes care of putting
all those jars where they need to be
> 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 _when working from svn or in using src releases_ 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 -- however we still need the
> build system capable of putting the actual jars into specific lib folders
> when assembling the binary artifacts
--
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]
