Return-Path: Delivered-To: apmail-ant-dev-archive@www.apache.org Received: (qmail 4538 invoked from network); 3 Feb 2004 16:42:54 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 3 Feb 2004 16:42:54 -0000 Received: (qmail 88954 invoked by uid 500); 3 Feb 2004 16:40:38 -0000 Delivered-To: apmail-ant-dev-archive@ant.apache.org Received: (qmail 88849 invoked by uid 500); 3 Feb 2004 16:40:37 -0000 Mailing-List: contact dev-help@ant.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Ant Developers List" Reply-To: "Ant Developers List" Delivered-To: mailing list dev@ant.apache.org Received: (qmail 88732 invoked from network); 3 Feb 2004 16:40:36 -0000 Received: from unknown (HELO exchange.sun.com) (192.18.33.10) by daedalus.apache.org with SMTP; 3 Feb 2004 16:40:36 -0000 Received: (qmail 29419 invoked by uid 50); 3 Feb 2004 16:40:53 -0000 Date: 3 Feb 2004 16:40:53 -0000 Message-ID: <20040203164053.29417.qmail@nagoya.betaversion.org> From: bugzilla@apache.org To: dev@ant.apache.org Cc: Subject: DO NOT REPLY [Bug 26364] - [PATCH] nested for PLUS composite X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: minotaur-2.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=26364 [PATCH] nested for PLUS composite ------- Additional Comments From peter.reilly@corvil.com 2004-02-03 16:40 ------- Using dynamic configuration to set the attributes of the embedded filename mapper class is a good idea. The may be used with custom tasks. It can only be used as an nested element to a element. For example the task can use it without any modification, as can the task from ant-contrib. On a general note, I never liked the design of mapper + filename mapper being one element with the specific filename mapper being specified by an attribute. This is different from the other customizer types - like selectors, filters and conditions. The mapper patch will allow new custom file name mappers to be defined and used like built-in mappers - as nested types in a container, deprecating the current type="x/y/z" usage. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org For additional commands, e-mail: dev-help@ant.apache.org