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 2003/08/15 15:34:52 UTC
DO NOT REPLY [Bug 22460] New: -
No access to the message output level from API
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=22460>.
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=22460
No access to the message output level from API
Summary: No access to the message output level from API
Product: Ant
Version: 1.5.4
Platform: All
OS/Version: Windows NT/2K
Status: NEW
Severity: Enhancement
Priority: Other
Component: Core
AssignedTo: dev@ant.apache.org
ReportedBy: petrovs@hotmail.com
Here is my situation : I'd like to control the amount of the info that my
custom task puts on the screen according to verbosity settings that user passes
in the commanline (-verbose, -debug etc.). The task itself is a wrapper around
the existing code that uses System.out/System.err and I can manipulate the
level of its' output with a set of proprietary parameters. But I can not match
them with Ant's message level since I have no access to it at runtime. It would
be nice to have something like Project.getMessageOutputLevel() that returns the
current message level set from the command line.
Of course my other alternative is to provide something like 'verbose' attribute
on my task but this is ugly since I have to explicitly set this flag every time
rather than automatically inheriting user settings.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org