Summary: | Aggregating filesets is *functionally* possible and would be very useful for large projects | ||
---|---|---|---|
Product: | Ant | Reporter: | Aleksandar Susnjar <asusnjar> |
Component: | Core | Assignee: | Ant Notifications List <notifications> |
Status: | NEEDINFO --- | ||
Severity: | enhancement | ||
Priority: | P2 | ||
Version: | 1.7.1 | ||
Target Milestone: | --- | ||
Hardware: | All | ||
OS: | All |
Description
Aleksandar Susnjar
2008-10-25 06:46:52 UTC
One more thing: why is this important? From my perspective, one differentiating factor between ant and other build software is that it can do what other, perhaps simpler-to-use, software cannot do. This leaves ant with the more complex scenarios, rather than the simple one. And in these complex scenarios, features that can enhance build script structure, maintenance and flexibility becomes very important. doesn't a <union>-ResourceCollection do the trick? Union does not seem to work for archive filesets. If I attempt to create a union of zipfilesets (so that I can reuse it to create a zip and a tar), the non-basic-fileset attributes appear to get lost in the union. For example, zipfileset.prefix is not used in the archive that gets created. (In reply to comment #3) > Union does not seem to work for archive filesets. If I attempt to create a > union of zipfilesets (so that I can reuse it to create a zip and a tar), the > non-basic-fileset attributes appear to get lost in the union. For example, > zipfileset.prefix is not used in the archive that gets created. Hmm, that shouldn't be the case. Any chance the <archives> collection works any better for you? A sample buildfile, particularly one presented in antunit form, would be very helpful. |