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 9481] - Add a "prefix" attribute to ExpandProperties filter to allow limiting expansion to certain properties.
Date Wed, 29 May 2002 11:22:10 GMT
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=9481>.
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=9481

Add a "prefix" attribute to ExpandProperties filter to allow limiting expansion to certain
properties.





------- Additional Comments From umagesh@apache.org  2002-05-29 11:22 -------
I didn't doubt that you would have taken the trouble to write the code without
a need fo rit ;-)  I just wanted it written in here so that we realize why this
enhancement is being requested...

By multiple prefixes, I mean the following:  say, the user wants to limit all
properties that begin with 'user' as well as 'system' from expansion.  Having it
as an attribute with comma-spearated values will not be very nice.  Instead we
would need nested elements.  On the same lines, let us say, I want to limit
expansion of all properties that begin with 'user', but not necessarily the
ones that begin with 'user.ant', then <include>, <exclude> elements might be 
nice.

The only reservation I have with 'prefix' it is not generic enough - for 
example, I may want to limit expansion of all properties that 'contain' the
string 'user.dir'... in which case my example would be written as <include
contains="user.dir"/>

With regards to <echoproperties> and consistency, you have a point there ;-)

--
To unsubscribe, e-mail:   <mailto:ant-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:ant-dev-help@jakarta.apache.org>


Mime
View raw message