I don't know what I was doing wrong, but I've now got the behavior I was
seeking. Very weird.
// Neil
- Original Message -
From: Ian MacLean
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Sent: Mon, 22 Nov 2004 12:06:18 +0900
Subject: Re: [nant-dev] Separating targets into individual files
I haven't really given it too much though, but I don't think we should have
a very long rc period. We should really try to release versions more
frequently, without sacrificing quality ofcourse.
I was just thinking about those people who can't use nightly builds
for corporate reasons, and
Hi Nicke,
good call I think. Verbosity problem is here, and I really want so solve it,
but I prefer to do it after release. I also think (and beleive others also)
we need shorter release cycle (aprox. 4 a year?)
1/: I didnt catch it - sorry. Structure of Nant's XML log is pretty vague -
thats
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On
Behalf Of Thibaut Barrère
Sent: maandag 22 november 2004 11:26
To: Gert Driesen
Cc: [EMAIL PROTECTED]
Subject: Re: [nant-dev] NAnt 0.85 release - how ?
I haven't really given it too much though, but I
ps : I've got a small nant function called is-assembly (to
determine
whether a file is a valid assembly or not). Is it worth
contributing ?
I'm using it to separate my legacy dll from assemblies. I know
there's the get-assembly-name trick, but maybe it's worth
it. Tell me
what
Martin Aliger wrote:
ps : I've got a small nant function called is-assembly (to
determine
whether a file is a valid assembly or not). Is it worth
contributing ?
I'm using it to separate my legacy dll from assemblies. I know
there's the get-assembly-name trick, but maybe
ok I'll push a patch tonight then
--Thibaut
---
SF email is sponsored by - The IT Product Guide
Read honest candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
NAnt 0.84 (Build 0.84.1455.0; net-1.0.win32;
release; 12/26/2003)
Copyright (C) 2001-2003 Gerry Shaw
http://nant.sourceforge.net
Buildfile: file:///C:/Inetpub/wwwroot/CCOM_Web/SupportFiles/TestBuild.build
Target(s) specified: Build
Build:
NantTestProject:
[solution] Starting solution build.
Brad,
Can you verify whether you still get the error using the latest nightly
build (http://nant.sourceforge.net/nightly/latest/) ?
Thanks !
Gert
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On
Behalf Of Brad Langhorst
Sent: zondag 21 november 2004 21:53
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On
Behalf Of Thibaut Barrère
Sent: maandag 22 november 2004 23:09
To: [EMAIL PROTECTED]
Subject: [nant-dev] is-assembly patch
Here's a patch implementing function
assembly::is-assembly(assemblyFilename).
good point! I put it in assembly in the patch, but now that you talk
about file, it sounds better. So I'd vote for file.
anyone else ??
On Mon, 22 Nov 2004 23:19:19 +0100, Gert Driesen
[EMAIL PROTECTED] wrote:
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL
Hi Matthew,
I've had another look at how our delete task is working right now, and the
more I think of it, the more I'm convinced that we should change it to match
the Ant delete task.
Right now, we remove all directories that are matched by the fileset. But
this does not respect any excludes.
12 matches
Mail list logo