I send you both files for the <record> task. Just tested them with latest version of NAnt and NAntContrib from cvs and they compile and works.
committed. Please be aware of the whitespace and formatting standards for nant - http://sourceforge.net/docman/display_doc.php?docid=6080&group_id=31650
otherwise its good. Thanks.
Just a question, why if the task path a ';' separated list and not simply child nodes of nantsettings, with a node for each directory ?
technically a ; seperated string is simpler than a set of child nodes. I'm not too bothered either way. There is a strong precedent for ; seperated paths - but a node for each directory is more explicit.
Ian
Nick
From: Ian MacLean <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
CC: "'N. V.'" <[EMAIL PROTECTED]>, [EMAIL PROTECTED], [EMAIL PROTECTED]
Subject: Re: [NAntC-Dev] NAnt.Optional.zip
Date: Thu, 03 Jul 2003 17:14:15 +0900
MIME-Version: 1.0
sorry for the confusion but :
we decided to keep the tasks in NAntcontrib for now and
move a bunch of them into nant - post 0.83 release - see the 'Namespaces and NAnt.Cnntrib tasks' post for details on what tasks will go where.
but don't worry the bullet remains bitten. I've rolled the changes that are in NAnt.optional.zip back into nantcontrib which is now building against current NAnt cvs. We will ship a nant contrib task assembly with nant for the upcoming release.
Nick:
But the record task doesn't work, it simply create an empty file and doesn't loag anything into it. Since I have an updated version, which works with the new logging system, i could sent it to you, after making some minors changes to reflect the namespace changes.that would be awesome. All I did was comment stuff until it compiled. If you have a version that works with the new logging system just send it to me and I'll commit.
Another thing, I had to move the dll's from the bin\optional directly into bin to have NAnt recognize the tasks.It should find them there. Are you running nant from \build\nant-0.8.3-debug\bin and does the nant.exe.config in that directory contain :
<nantsettings
defaultframework="net-1.0"
taskpath=".\optional">
taskpath allows you specify a ';' seperated list of directories that contain task assemblies. You may need to cvs update nant as well to get the taskpath related changes.
Ian
further 2 cents:
1) thanks for biting the bullet, very much! 2) does it make sense that nantcontrib ends up in a single dll as opposed to several dlls, smaller, per task set? seems to me it might complicate the configuration a little bit more, but would yield easier to handle subproject (eg: if one task is broken, the whole thing isn't broken...)
/jean
------------------------------------------------------- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa00100006ave/direct;at.asp_061203_01/01 _______________________________________________ NAntContrib-Developer mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nantcontrib-developer
