Hi, +1 for outputting the target framework
Gary, would the quiet (-q) switch solve the verbosity issue? If you are looking for even less output there are other commandline tools that also add another quiet switch (really quiet) or a "silent" switch to cut down on messages logged. Also for the <log /> task, I am not sure if this is in line with what you were thinking but the <echo /> task already takes a logging level (optional) and filename (optional), would this serve the same purpose? Maybe an extension to include a collection/ array of <message/> elements? I am just offering suggestions and trying to understand the issue (because I don't think the output is too verbose :-)) so please feel free to fire back with specifics. Cheers, Clayton -----Original Message----- From: Gary Feldman [mailto:[EMAIL PROTECTED] Sent: Wed 9/15/2004 12:43 PM To: Nant-Developers (E-Mail) Cc: Subject: Re: [nant-dev] Output target framework at startup ? >From: "Gert Driesen" <[EMAIL PROTECTED]> >Sent: Wednesday, September 15, 2004 2:04 PM > Hi, > > I wonder if we should output the name of the target framework when starting > a build, and perhaps also output it again whenever you change the target > framework > > What do you think ? NAnt's verbosity has been the subject of much discussion (not just me - e.g. a recent post on the user's list that mentioned postprocessing the NAnt xml log to make it reasonable). I think that adding more output unconditionally must be considered carefully, especially since many people are probably already printing out such info on their own. Suppose instead there were a <log> task, where <log /> would put out some default info, while <log> <logitem name="framework-version" /> <logitem name="targets" /> <logitem name="nant-version" /> <logitem name="timestamp" /> <logitem name="hostname" /> <logitem name="host-os" /> <logitem name="command-line-defs" /> <logitem name="project-file-date" /> </log> would do the obvious. This would give the user much more control over logging, and furthermore, would solve the problem of recursive nant invocations producing redundant log info (by simply allowing the user to omit the <log> task from the subordinare nant files). It would also provide a structure for future enhancement. Gary ------------------------------------------------------- This SF.Net email is sponsored by: thawte's Crypto Challenge Vl Crack the code and win a Sony DCRHC40 MiniDV Digital Handycam Camcorder. More prizes in the weekly Lunch Hour Challenge. Sign up NOW http://ad.doubleclick.net/clk;10740251;10262165;m _______________________________________________ nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers ------------------------------------------------------- This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170 Project Admins to receive an Apple iPod Mini FREE for your judgement on who ports your project to Linux PPC the best. Sponsored by IBM. Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php _______________________________________________ nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
