Mailing-List: contact dev-help@ant.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Ant Developers List" <dev@ant.apache.org>
Date: Fri, 7 Jan 2005 00:36:35 +0100
Message-Id: <200501062336.j06NaZFr009201@ajax.apache.org>
From: bugzilla@apache.org
To: dev@ant.apache.org
Subject: DO NOT REPLY [Bug 5035]  -
    Patternset and fileset enhancements

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG�
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=5035>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND�
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=5035


------- Additional Comments From arnold@moonhill.org  2005-01-07 00:36 -------
I'm not seeing the problem.  Let's take something concrete: two filesets, one rooted in /a/b/c (id is "C"), and 
another rooted in /a/b/x (id is "X").  Now let's create a new fileset "U" that contains "C" and "X".

When a task (say, replace) asks "U" for its dir, it will get "/a/b".  When it asks for files from that set, it will 
get "c/foo.java" and "x/bar.java" or whatever.  This can be done on the fly -- when the method that returns 
files from the fileset returns them, it can know what to prepend to the files returned by its nested sets, 
depending one whether it's reading from "C" (where it prepends "c/") or X ("x/").

To me this seems to be make each fileset behave as expected, and fulfill the contract.  Maybe I'm missing 
something.

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org