Hi all, I'm not really sure what the task is going to be used for, that's probably my biggest problem with it. Why do we need it?
The problem Bug 32631 talks about could better be solved by tasks that perform set operations. Right now our best file collection is path and it would be rather easy to have <intersect targetid="new-path"> <path refid="path1"/> <path refid="path2"/> </intersect> as a task that creates a new path based on the intersection of two others. Set unions are already possible for <path>. Set minus should be as easy to implement as intersections. Writing the same things for filesets would be possible as well, but we'd sooner or later run into duplications. Maybe we really need to finally tackle a generic file collection approach that unifies fileset, path and filelist (possibly path is that already?) and have tasks that work on those collections. Stefan --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
