ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject [Bug 2111] - Request mechanism to indicate progress while logging
Date Mon, 30 Jul 2001 16:44:19 GMT
PLEASE DO NOT REPLY TO THIS MESSAGE. TO FURTHER COMMENT
ON THE STATUS OF THIS BUG PLEASE FOLLOW THE LINK BELOW
AND USE THE ON-LINE APPLICATION. REPLYING TO THIS MESSAGE
DOES NOT UPDATE THE DATABASE, AND SO YOUR COMMENT WILL
BE LOST SOMEWHERE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=2111

*** shadow/2111	Mon Jul 30 09:17:10 2001
--- shadow/2111.tmp.26084	Mon Jul 30 09:44:19 2001
***************
*** 43,46 ****
  for me but certainly isn't a generic solution. All I wanted to do was use the 
  <echo> task to indicate the target and task I was currently executing, that way 
  I'd have a sense of where I was, or a progress if you will, in the build 
! process.
--- 43,68 ----
  for me but certainly isn't a generic solution. All I wanted to do was use the 
  <echo> task to indicate the target and task I was currently executing, that way 
  I'd have a sense of where I was, or a progress if you will, in the build 
! process.
! 
! ------- Additional Comments From donald_l_taylor_jr@yahoo.com  2001-07-30 09:44 -------
! Have you folks considered using Jakarta's log4j? It would solve this problem, 
! plus a whole lot more. You could have a -logcfgfile command-line argument where 
! you can point to an optional log configuration file where you can setup the 
! logging however you want.
! 
! People have always complained about using the -verbose option and getting more 
! information than they really need. Problem solved. If you follow the guideline 
! of each class being its own category, you could specify a logging configuration 
! where I only see the verbose output for the tasks I choose.
! 
! You want e-mail notification? Setup an SMTPAppender. You could also log to a 
! database, to an external logging server (using SocketAppender), anything you 
! want. The beauty is the ant source wouldn't have to change dramatically to 
! support it. Once you add in the logging facility the user can pretty much do as 
! he pleases.
! 
! Of course you'd have to have a default configuration file to support current 
! ant behavior, but that wouldn't be too hard to do.
! 
! Seems like log4j would solve several of ant's problems. How 'bout it?

Mime
View raw message