Summary: | pattern / nested patternset in filterset | ||
---|---|---|---|
Product: | Ant | Reporter: | Holger Engels <hengels> |
Component: | Core tasks | Assignee: | Ant Notifications List <notifications> |
Status: | REOPENED --- | ||
Severity: | enhancement | ||
Priority: | P2 | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Hardware: | PC | ||
OS: | Linux |
Description
Holger Engels
2004-12-10 14:06:08 UTC
You can do this with multiple copy tasks. (In reply to comment #1) > You can do this with multiple copy tasks. I can use multiple coüpy tasks only, if I am the one, who defines the fileset. Unfortunately, I'm not. The fileset is an artifact, exported by another module. The documentation of filtersets says "copy operations will typically corrupt binary files". But there's no straight forward way to avoid that. Imagine you write a deploy target, that copies filesets to a deployment directory and thereby weaves the configuration into the deployables. From the perspective of the target, filesets are logical units. The target should be unconcerned about the fileset's internals. .. just wanted to state my thoughts. I won't reopen the issue again. It still sounds as though you could work around this using multiple copy operations if you had the ability to use an existing fileset as a template for a more-specific fileset, per your other bug report, correct? Correct. Then I could write something like: <copy todir="${deploy.dir}"> <fileset inherit="webapp"> <include name="**/*.xml"/> </fileset> <filterset> <filter token="DATE" value="${TODAY}"/> </filterset> </copy> <copy todir="${deploy.dir}"> <fileset inherit="webapp"> <exclude name="**/*.xml"/> </fileset> </copy> |