Every task should at least output somthing for each unit of work its doing - unloess its very fine grained. If it outputs nothing then you never see the [taskname] so its hard to know if that task has run at all.
Ian


Hi again (hope last one today)
I found verbosity level of many tasks very inconsistent. Maybe we could say how much task should output under normal run and other messages move into verbose level.
for example solution task with only 2 assemblies to compile (without warning) outputs:
[solution] Starting solution build.
[solution] Building Gordic.General [Release]...
Read in 11 resources from 'c:\temp\build-src\Gordic.Gene
ral\Gordic.General.resx'
Writing resource file... Done.
[solution] Building Gordic.Support.Win32 [Release]...
Read in 5 resources from 'c:\temp\build-src\Gordic.Suppo
rt.Win32\Gordic.Support.Win32.resx'
Writing resource file... Done.
where plain
[solution] Building Gordic.General [Release]...
[solution] Building Gordic.Support.Win32 [Release]...
should be enough.
In opposite e.g.
<delay-sign> outputs _nothing_ even when signing over 100 assemblies (in verbose mode it outputs 10 lines per assembly)
I think something like copy's [copy] Copying 17 files to c:\temp\build-src. should be outputted.
[delay-sign] 117 assemblies was delay signed.
Regards,
Martin






-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive?  Does it
help you create better code?  SHARE THE LOVE, and help us help
YOU!  Click Here: http://sourceforge.net/donate/
_______________________________________________
nant-developers mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-developers

Reply via email to