Return-Path: Mailing-List: contact dev-help@ant.apache.org; run by ezmlm Delivered-To: mailing list dev@ant.apache.org Received: (qmail 85261 invoked from network); 13 Feb 2003 11:53:08 -0000 Received: from exchange.sun.com (192.18.33.10) by daedalus.apache.org with SMTP; 13 Feb 2003 11:53:08 -0000 Received: (qmail 11464 invoked by uid 50); 13 Feb 2003 11:54:38 -0000 Date: 13 Feb 2003 11:54:38 -0000 Message-ID: <20030213115438.11463.qmail@nagoya.betaversion.org> From: bugzilla@apache.org To: dev@ant.apache.org Cc: Subject: DO NOT REPLY [Bug 8654] - No ..'ing below fileset base X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . 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=8654 No ..'ing below fileset base jefft@apache.org changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|Normal |Enhancement ------- Additional Comments From jefft@apache.org 2003-02-13 11:54 ------- Yes, can't think why I marked it 'bug' rather than 'enhancement'. IIRC, the point I wanted to make was that the implementation is overly restricting the semantics. Conceptually, why shouldn't be generalized from "a set of files below x" to "a set of files whose path starts with x"? Makes perfect sense to me as a user. Imagine if bash disallowed 'ls ../*'. *Practically*, this is all marsh gas; futzing with the API would kill backwards-compat. But why let reality get in the way when filing bugreports :o) --Jeff