----- Original Message -----
From: "Ian MacLean" <[EMAIL PROTECTED]>
To: "Nant-Developers (E-mail)" <[EMAIL PROTECTED]>
Sent: Thursday, July 08, 2004 5:28 AM
Subject: [nant-dev] current cvs build failure


> A fresh cvs checkout of nant is failing with the following :
>
>      [echo] Running unit tests with just built version of NAnt.
>      [exec]
> H:\cvs\nant-test\nant/build/net-1.1.win32/nant-0.85-debug/bin/NAnt.exe
> -buildfile:NAnt.build debug self-test -D:proje
> ct.version=0.85 -targetframework:net-1.1
>             NAnt 0.85 (Build 0.85.1650.0; net-1.1.win32; nightly;
7/8/2004)
>             Copyright (C) 2001-2004 Gerry Shaw
>             NAnt Team
>
>             BUILD FAILED
>
>
>             For more information regarding the cause of the build
> failure, run the build again in debug mode.
>
>             Try 'nant -help' for more information
>             The current runtime framework 'net-1.1' is not correctly
> configured in the NAnt configuration file.
>                 Invalid element <readregistry>. Unknown task or datatype.
>
> BUILD FAILED
>
> H:\cvs\nant-test\nant\NAnt.build(160,10):
> External Program Failed:
> H:\cvs\nant-test\nant/build/net-1.1.win32/nant-0.85-debug/bin/NAnt.exe
> (return code was 1)
>
> This is new since yesterday - Does anyone who checked in code in the last
day have an idea ?

I think there's an issue with the DirectoryScanner changes that Matthew
committed yesterday.

Matthew, can you have a look at this (possibly write some more unit tests,
so we don't have any regression on this in the future) ?

Thanks,

Gert



-------------------------------------------------------
This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 - 
digital self defense, top technical experts, no vendor pitches, 
unmatched networking opportunities. Visit www.blackhat.com
_______________________________________________
nant-developers mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-developers

Reply via email to