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=29011>. 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=29011 Enhance the <copy/>-tag to support filesets for both source *and* destination ------- Additional Comments From [EMAIL PROTECTED] 2004-05-17 12:44 ------- I could easily avoid the need, as I can write multiple copy statements. What I would like to see: <copy someparam="somevalue"> <src> <fileset dir="."> <include name="${copyfilename.file}"/> </fileset> </src> <dest> <dirset dir="."> <include name="*"/> <dirset> </dest> </copy> The question is; why not? Maybe not many people need it, but still it's handy and last but not least: it's consistent. Why am I able to define a nested fileset for the source then? That's also not really needed, I could also write multiple copy statements for that. You don't see the need, *except* .... The latter is just the need. Practical example: you want to keep 2 or more build output dirs, for some reason. It just opens up possibilities which will greatly reduce the footprint of the build.xml file in some cases. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
