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 32827] New: - Request for option to fail when filter tokens undefined
Date Thu, 23 Dec 2004 10:08:29 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=32827>.
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=32827

           Summary: Request for option to fail when filter tokens undefined
           Product: Ant
           Version: 1.6.1
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: enhancement
          Priority: P3
         Component: Core tasks
        AssignedTo: dev@ant.apache.org
        ReportedBy: james@xini.com


Would it be possible to add a feature to the various tasks that use filtering to
fail when a token is recognised in the file being copied, but there is no value
defined for that token. e.g. a "failOnUndefToken='true'" attribute). The present
behaviour of passing the token through unmodified may be good in many
situations, but we've found it all too common for someone to add a new token to
the file but then people building the code forget to add the token to their
filtersfile - it would be good for this to fail at build time rather than runtime.

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