I'm wondering if there has been any dicussion of using the DOM as a model for filesets? In which case XPath or some variant could be used instead of ant's proprietary fileset syntax. Example: "xx//yy" instead of "xx/**/yy", meaning "all yy descendants of xx". The DOM and virtually every file system is based on a tree model. Node references could model symbolic links. And attribute nodes in the DOM could be used to model file and directory attributes. Example: "*[@type='file' and @read-only!='true']" meaning "all files that are not read only". The entire file system structure would NOT have to be loaded into memory, as the DOM specifies an interface, not a storage structure.
Glenn McAllister wrote: > "Frazier, Scott" wrote: > > > Hi, > > Does ant 1.4 support the notion of deleting a symbolic link as > > opposed to the file/directory the symlink points to? I know I can use the > > exec task, but I'd rather avoid that if possible. > > Not at the moment, no. There have been a number of discussions about using > cannonical filename and whatnot to distinguish between symlinks and the actual > files, but I don't recall what came of them. There was an issue that wasn't > resovled with that algorithm if I remember correctly. > > Glenn McAllister > SOMA Networks, Inc.
