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 27568] New: - filtertask doesn't respect loglevel
Date Wed, 10 Mar 2004 14:58:40 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=27568>.
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=27568

filtertask doesn't respect loglevel

           Summary: filtertask doesn't respect loglevel
           Product: Ant
           Version: 1.6.1
          Platform: All
        OS/Version: Other
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: Core tasks
        AssignedTo: dev@ant.apache.org
        ReportedBy: marcel@schutte.com


Filters that are defined at either projectlevel or targetlevel, produce 
messages of the form 'Replacing: @token@ -> replacement' irrespective of the 
loglevel being used (-quiet, -verbose or -debug). When the filter is part of a 
filterset it works as expected and only logs for levels -verbose and -debug.

I have verified with a debugger that for a standalone filtertask the 'project' 
attribute in the ProjectComponent object is null which causes 
ProjectComponent,log() to log everything above Project.MSG_INFO. In the case 
where the filter is part of a filterset, the 'project' attribute is set and 
logging works as expected.

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


Mime
View raw message