You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ant.apache.org by bu...@apache.org on 2003/06/11 20:35:25 UTC
DO NOT REPLY [Bug 20687] New: -
[PATCH] Enhance ExecOn with DirSets
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=20687>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=20687
[PATCH] Enhance ExecOn with DirSets
Summary: [PATCH] Enhance ExecOn with DirSets
Product: Ant
Version: 1.6Alpha (nightly)
Platform: All
OS/Version: All
Status: NEW
Severity: Enhancement
Priority: Other
Component: Core tasks
AssignedTo: dev@ant.apache.org
ReportedBy: gus.heck@olin.edu
As per my corespondance with Stefan on the dev list,
http://marc.theaimsgroup.com/?l=ant-dev&m=105367047624558&w=2
I have added dirset support to ExecOn.java (and thus to attrib, chmod, chgrp,
and chown). Making it work and not messing up the old type=file but not
requiring type=dir to use dirsets took a little thinking. I settled on an
implementation that esentially checks to see if it is handling a dirset and
gives the nested dirset priorety over the type="file". This seems to provide
full back compatability and the nice feature that you can still control the
behavior of filesets with type="file" and then slip in a few directories with a
dirset.
The cost of course is that reading type="file" in the top line of a long chmod,
nolonger guarantees that nothing below represents a directory, but only
specifies how filesets will be handled.
Not specifying type is the same as specifying type="file" so people who just
want to use a dirset can just use it.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org