Re: [Nant-users] "if" attribute on mkdir ignored

2005-08-22 Thread Gert Driesen
- Original Message - From: <[EMAIL PROTECTED]> To: Sent: Monday, August 22, 2005 6:59 PM Subject: [Nant-users] "if" attribute on mkdir ignored > I am running RC3 and the following build source fails: > > > > > > > if="${string::get-length(empty) != 0}" /> > > > > > I get the f

RE: [Nant-users] nUnit2 task: Remove from project

2005-08-22 Thread Brass Tilde
> I can see the point behind this, and to an extent I agree: if a feature is broken and there's no intention of fixing it then it > should simply be removed, because otherwise people (like me - see my earlier post) are going to waste a lot of time trying to > get something to work that just won't

RE: [Nant-users] nUnit2 task: Remove from project

2005-08-22 Thread angus.grant
I use nAnt all the time for all our companies projects. But I must admit I am a bit of a lazy user, simply pointing nAnt to our solution files to build debug or release versions depending on choice, a clean up task, another task to create install packages, nUnit testing, and nCover tests as

[Nant-users] "if" attribute on mkdir ignored

2005-08-22 Thread Tony_Bjerstedt
Title: "if" attribute on mkdir ignored I am running RC3 and the following build source fails:                                         I get the following output: NAnt 0.85 (Build 0.85.1932.0; rc3; 4/16/2005) Copyright (C) 2001-2005 Gerry S

RE: [Nant-users] nUnit2 task: Remove from project

2005-08-22 Thread Bart Read
I can see the point behind this, and to an extent I agree: if a feature is broken and there’s no intention of fixing it then it should simply be removed, because otherwise people (like me – see my earlier post) are going to waste a lot of time trying to get something to work that just won’t