Hi Dustin,
To include a file of property definitions use the include task.
http://nant.sourceforge.net/nightly/help/tasks/include.html
Just create a build file that contains only property definitions.
Somthing like:
project name=common build properties
!-- place global properties here --
I'd like to propose a new function set that would help solve the issue of
generating a classpath from a list of files. The functions deal with named
filesets like this:
project
fileset id=zzz
includes name=*.cs /
/fileset
fileset id=rrr
includes name=*.csu7987987 /
We're in the process of upgrading to 0.84 from 0.81. I found what appears
to be a problem with the NUnit1 task. It no longer creates the test output
files. I tried several variants of the task and couldn't get it to function
correctly, so I took a look at the code.
It seems that the
These look cool. I wonder should fileset::exists be fileset::contains ?
by definition if its in the fileset it must exist. Would somthing like
fileset::rescan() also be useful ?
Ian
Jaroslaw Kowalski wrote:
I'd like to propose a new function set that would help solve the issue of
generating
Any,
I committed your fix to cvs, however I would advise you to upgrade to NUnit
2.x asap.
Gert
- Original Message -
From: Andy Sipe [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Friday, March 19, 2004 4:46 PM
Subject: [nant-dev] problem with NUnit1 Task
We're in the process of
Please don't call it flatten.
That's already used in the context of taking files from subdirectories
and placing them in one single directory.
On the other hand the ability to arbitrarily take a list of items and create
a
single delimited array would be useful to me. I already have C# embedded
Just one quick idea:
what about possibility to construct fileset back from this flatten file
list?
fileset id=zzz
includes name=*.cs /
/fileset
property name=flist value=${fileset::flatten('zzz',';')} /
fileset id=ggg
includes list=${flist} /
/fileset
OK. I'd like to gather current ideas (with some minor modifications) with
one-line summaries:
fileset::exists(id) - checks whether fileset named id is defined in
current project
fileset::get-file-count(id) - returns the number of files matched by the
fileset id
fileset::is-empty(id) - checks
fileset::to-string(id,separator) - returns a list of files from the
fileset 'id' separated by 'separator'
Very happy with this naming here.
-Peter
-Original Message-
From: Jaroslaw Kowalski [mailto:[EMAIL PROTECTED]
Sent: Friday, March 19, 2004 1:01 PM
To: Ian MacLean; Horsfield,
On Fri, 2004-03-19 at 19:26, John Luke wrote:
On Fri, 2004-03-19 at 19:14 +0100, Giuseppe Greco wrote:
I do not agree!
Just download the following sample application and
try to build it with the latest version of nant:
http://developer.agamura.com/resources/thermota-0.6.src.tar.gz
3. does nant support building C?
Just ask it to the NAnt community: Ian, Gert, Jarek, is there any
plan to build C support in NAnt?
I don't think it's a good idea for NAnt to directly support C compilation or
even C compiler invocation, just because it's s complex (just look at
the size
Gert,
Thanks -- we're hoping to start converting to NUnit2 soon.
I found another problem with the NUnit1 task. The haltonerror and
haltonfailure attributes are being used incorrectly by the task. It is my
understanding that those properties should throw a build exception when they
are true
I was having this same problem! Thanks for the script.
+1 for a ant task
brant
...
From: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: [nant-dev] New to the list
Date: Fri, 19 Mar 2004 08:57:55 -0500
Hi everyone! I joined this list because there are some differences between
Nant and
Looks good. I see I misread the intent of exists() initially. These will
be very useful. Good work Jarek
Ian
Jaroslaw Kowalski wrote:
OK. I'd like to gather current ideas (with some minor modifications) with
one-line summaries:
fileset::exists(id) - checks whether fileset named id is defined
14 matches
Mail list logo
