ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 5035] - Patternset and fileset enhancements
Date Thu, 06 Jan 2005 23:31:44 GMT
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 ddevienne@lgc.com  2005-01-07 00:31 -------
I'm not sure I'm following you ;-)

If you allow creating such filesets, people will use them in <javac> and <copy>

and custom tasks and get NPEs from those tasks, no?

The fact is that in Ant a FileSet is not just a set of files, although many 
tasks treat it as such, but it's more a set of relative filenames, from a given 
directory.

By allowing to have a null directory, you're fundamentally changing the fileset 
contract. Sure you could change Ant's classes like Javac to refuse such special 
null dir filesets, but what about tasks outside Ant?

This is why I keep on saying this can't be done in a BC friendly way. But I've 
been wrong many times before ;-) --DD

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


Mime
View raw message