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

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

I'm not sure we should really go to the trouble for this issue.

why can't developers just 'ant clean-jars' after they svn update? Really we are 
just talking about committers etc tracking development branches here: they 
should be subscribed to the commits@ list and watching what is happening. Jar 
upgrades should be no surprise.

The problem with doing all this automagic stuff is it makes things too 
automagic: what if i just want to plop in a jar today to test it before dealing 
with maven etc? This works completely fine today: but if we start rm'ing jars 
in 'resolve' then this becomes impossible.

if anything gets done on this issue, then personally i want it triggered by a 
property that is completely defaulted to 'off'. If you want it on, put it in 
your ~/build.properties etc.
                
> 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