ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Conor MacNeill" <co...@m64.com>
Subject RE: Recent logging aint emacs friendly
Date Sat, 08 Jul 2000 13:26:16 GMT
> -----Original Message-----
> From: Ernst de Haan [mailto:ernst@jollem.com]
> Sent: Saturday, 8 July 2000 23:22
> To: ant-dev@jakarta.apache.org
> Subject: Re: Recent logging aint emacs friendly
>
>
> <snip>
> > > Hmm, perhaps the logger can be specified as a parameter for the root
> > > element in the build file.
> </snip>
> <snip>
> > I don't think this would be good. The logger to be used in a
> build is not
> > really a property of the project. A PI makes some sense but I
> still think
> > this should be specified outside the project file. Logging is
> something the
> > user running ant is worried about, not the author of the build file. My
> > preference would therefore be to use a command line parameter.
> </snip>
>
> Yup. You are right. It must be known before the build.xml is actually
> parsed, because the setting will influence the output from the start on.
> So I agree a command-line option would be the answer.
>
> <snip>
> > 1. add a parameter to ant which causes the default listener to
> produce emacs
> > friendly output.
> > 2. allow the logger class to be specified on the command line and then
> > provide an emacs friendly logger.
> > 3. combine 1 and 2.
> </snip>
>
> What exactly do you mean by the first option ?
>

Option 1 boils downs to a single logger class which has two behaviours
controlled by the command line parameter.

Option 2 is 2 logger classes with separate behaviours.

Conor


Mime
View raw message