lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dawid Weiss (JIRA)" <>
Subject [jira] [Commented] (LUCENE-4115) JAR resolution/ cleanup should be done automatically for ant clean/ eclipse/ resolve.
Date Fri, 08 Jun 2012 21:47:24 GMT


Dawid Weiss commented on LUCENE-4115:

Hoss -- I've been doing some experiments with ivy (and I know very little about it) but it
seems that you can use ivy to build both <path> elements and <fileset> elements
from the same configuration. This means you would construct an identical path for any java
invocation/ taskdef, etc. and a fileset for <copy> to lib/.

I agree with you 100% that we shouldn't be doing any copying or filtering manually -- it has
to be the same fileset.

We could even use the fileset only and just put it under a custom <path id="..."> element.

Note that at the moment this isn't consistent either -- if there is a jar dependency upgrade
people are left with unused jars under lib/* and this can (and does) cause headaches until
you realize you need to clean up that folder (which is a reason for this issue, actually).
> JAR resolution/ cleanup should be done automatically for ant clean/ eclipse/ resolve.
> -------------------------------------------------------------------------------------
>                 Key: LUCENE-4115
>                 URL:
>             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:!default.jspa
For more information on JIRA, see:


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

View raw message