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 32632] - pattern / nested patternset in filterset
Date Mon, 13 Dec 2004 07:29:10 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=32632>.
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=32632


hengels@mercatis.de changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
         Resolution|WORKSFORME                  |




------- Additional Comments From hengels@mercatis.de  2004-12-13 08:29 -------
(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.


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