[ 
https://issues.apache.org/jira/browse/LUCENE-4115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13292419#comment-13292419
 ] 

Robert Muir commented on LUCENE-4115:
-------------------------------------

{quote}
For better or worse, that's the reason we have them – to specify dependencies.
{quote}

Not exactly true. in the current build, what is in lib/ specifies the 
dependencies.

ivy files are just being used as jar-downloaders.

                
> JAR resolution/ cleanup should be done automatically for ant clean/ eclipse/ 
> resolve.
> -------------------------------------------------------------------------------------
>
>                 Key: LUCENE-4115
>                 URL: https://issues.apache.org/jira/browse/LUCENE-4115
>             Project: Lucene - Java
>          Issue Type: Task
>            Reporter: Dawid Weiss
>            Assignee: Dawid Weiss
>            Priority: Trivial
>             Fix For: 4.0, 5.0
>
>         Attachments: LUCENE-4111.patch, LUCENE-4115.patch
>
>
> I think we should add the following target deps:
> ant clean [depends on] clean-jars
> ant resolve [depends on] clean-jars
> ant eclipse [depends on] resolve, clean-jars
> ant idea [depends on] resolve, clean-jars
> This eliminates the need to remember about cleaning up stale jars which users 
> complain about (and I think they're right about it). The overhead will be 
> minimal since resolve is only going to copy jars from cache. Eclipse won't 
> have a problem with updated JARs if they end up at the same location.
> If there are no objections I will fix this in a few hours.

--
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]

Reply via email to