Hi Martin,
I agree that it can be useful to control a log level threshold on a task
level. A property to control the logging threshold of a Task actually
already exists (Task.Threshold), but I have chosen not to expose this
attribute to build authors yet, as I first want to discuss this further.
I think it would also be great to have a way to control the log level with
which certain messages are output on a task-level. Meaning, certain messages
to which no explicit log level is assigned, would by default be logged with
level Info, but an additional attribute could be added to control the log
level of these messages. For example: you could increase the weight of these
messages to "Warning", or decrease them to "Debug".
But, again : this would need to be discussed further.
About the <delete> task : I've actually proposed to change this behaviour a
long time ago. In my opinion, the <delete> task should never fail if the
directory that you want to delete does not exist. That would also match the
behavior of Ant. Perhaps we should open that discussion again.
Gert
----- Original Message -----
From: "Martin Aliger" <[EMAIL PROTECTED]>
To: "'Gert Driesen'" <[EMAIL PROTECTED]>; "'! nant'"
<[EMAIL PROTECTED]>
Sent: Monday, October 11, 2004 12:21 PM
Subject: RE: [nant-dev] Re: task verbosity
> Hi all,
>
> I just found one situation where proper verbosity setting is necessary.
>
> Suppose this very simple target
> <target name="clean">
> <delete dir="${output.dir}" failonerror="false"/>
> <delete dir="${tests.dir}" failonerror="false"/>
> </target>
>
> is called from some automated environment (say CC.NET). Normally those
> folders should exist and no message is written. But when something goes
> wrong and folders are missing message
> "Cannot delete directory 'c:\foo\test'. The directory does not exist." is
> emmited with level "Error".
>
> This _is_ problem in automated environments because they suppose all
> messages with such level be errors and display them in red to users (or
> email about it).
>
>
> With simple <delete dir="${output.dir}" failonerror="false"
> verbosity="None"/> I'm saying that I'm aware that task could fail but I
dont
> mind.
>
>
> What do you think? (I don't hang over 'verbosity' name of course :-)
>
> Martin Aliger
>
>
> > > Hi Gert,
> > >
> > > do you somehow implement that message level stuff I
> > proposed some time
> > ago?
> > >
> > > I mean those:
> > > <exec program="c:\program files\subversion\bin\svn.exe"
> > > commandline="revert -R ${build.dir}" verbosity="Error"/>
> > > <exec program="c:\program files\subversion\bin\svn.exe"
> > > commandline="update ${build.dir}" verbosity="Info"/>
> >
> > No, that hasn't been implemented yet. I'm also ensure about
> > how it should
> > work in the first place.
> >
> > So we'll need to discuss this a lot further before thinking about
> > implementating it ...
>
> > Gert
>
>
>
-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl
_______________________________________________
nant-developers mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-developers
