Kelly I would strongly recommend implementing log4j to enable logging capabilities for your application To quote "The target of the log output can be a file, an OutputStream, a java.io.Writer, a remote log4j server, a remote Unix Syslog daemon, or even a NT Event logger among many other output targets." Take a look at http://logging.apache.org/log4j/docs/ to get you started HTH, Martin ----- Original Message ----- From: "Kelly Davis" <[EMAIL PROTECTED]> To: "Ant Users List" <[EMAIL PROTECTED]> Sent: Thursday, October 14, 2004 11:31 AM Subject: Re: setErrorPrintStream on DefaultLogger not working
> perhaps I should re-state the question a little bit. > > The problem that I am trying to solve is to be able to get compile > errors to a log file. When I run a build script using the ant task, and > set output= to a file, and the build script has compile errors, these > errors do not show up in the file specified in output, though I see them > on the console. The script will be running unattended using the api, so > it is important to be able to send the build error output somewhere > other than System.err. I would prefer this happen within the build > script and not in my code, but if necessary I will use the api. > > Kelly Davis wrote: > > > I am using ant 1.6.2 doing a build through the api. > > I am creating an instance of DefaultLogger. When I call > > setErrorPrintStream to a file for output, and then have a build with a > > compile error in it, the error output doesn't go to the file, but to > > my console. Any ideas on why this may be happening? > > > > Kelly > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
