You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ant.apache.org by bu...@apache.org on 2002/05/24 11:30:23 UTC
DO NOT REPLY [Bug 9378] New: -
Filters don't resolve nested filters..
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=9378>.
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=9378
Filters don't resolve nested filters..
Summary: Filters don't resolve nested filters..
Product: Ant
Version: 1.6Alpha (nightly)
Platform: Other
OS/Version: Other
Status: NEW
Severity: Major
Priority: Other
Component: Core tasks
AssignedTo: ant-dev@jakarta.apache.org
ReportedBy: martin@isallineed.org
Since I don't get any responce via the dev mailinglist, here you have a bug.
If the value of a filter token, contains another token, it will not be
resolved. I am only using a property filter file, which has values like this :
db.path=/usr/local/db
db.control=@db.path@/control
etc,etc,etc.
In the current situation the db.path on the db.control line will not be
resolved.
I am attaching a path for this to work and a test case (which is independend of
the testcases that already exist for the FilterSet. The naming can be a bit
confusing, so feel free to rename the testcase..
I really badly need this, I don't care in which version, as long as it is in
cvs.
Some info about the patch :
- Nested tokens calls will be resolved
- When an infinite loop could occur, it will return the originating token
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>