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 ------- Additional Comments From [EMAIL PROTECTED] 2003-08-15 17:39 ------- Here is the problem. The output level choice in ant is a final decision made by the output listeners and loggers, not something that is actually known by the logging components you call at logging time. This is different from log4j and siblings where you can go log.isDebug(). That said, I think the project does know what its invocation parameters are and there is no reason why the command line choice cannot be stored somewhere. One thing I have been debating doing, so as to control the amount of info generated by some Axis tasks that log via commons-logging, is to write a commons logging compatible logger that routes all log info to the ant logger. I will try working on this again; it may need some tweaks to the commons logger itself. If we add this, and your code moves to the commons logger API (a good practise, IMO), then you could leverage this functionality. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
