Hi Bill,
We are currently extending fileset to enable add something to existing
fileset. So your copy with two filesets could be rewritten into our concept
as:
copy
todir=${project.source.root}\${application.architecture.serviceinterface.bi
n.directory}
fileset refid=common.files
Martin Aliger:
We are currently extending fileset to enable add something to existing
fileset.
Yes, that would work for the example I sent (I thought about your recent
posts after I sent my email). After sending, I realized that the
refactoring I was doing also needed to do something like this
Hmm. Good point. Merging two filesets into third one...
In fact I'd added also this (but don't think it will be needed. Maybe it
will be!):
copy todir=\foo\one
fileset
includeFileset refid=common.files /
includeFileset refid=less.common.files /
/fileset
/copy
or
You mean the same task used for cleaning? Why?
csc output=... buildmode=clean
/csc
Jarek
I don't mind, but we should perhaps consider having a buildmode or
something, which can be set to Build (default), Rebuild, Clean,
Gert
---
because tasks know how to clean their output, so instead of having a clean
target we could actually have a clean mode ...
But I'm just thinking out loud here ...
Gert
- Original Message -
From: Jaroslaw Kowalski [EMAIL PROTECTED]
To: Gert Driesen [EMAIL PROTECTED]
Cc: ! nant [EMAIL
If may be so bold as to add some more to this...
I've been thinking of the same thing for the solution task. In VS it's
possible
to choose Rebuild etc., Nant should add rebuild and clean as virtual
targets.
It would be a great contribution if all tasks like it could do the same.
Good thinking
I just updated bug #875664, with a bit more detail. Does anyone have any
suggestions on what the appropriate fix for this problem might be? I am
dead in the water as long as this problem exists.
Thanks
-Mark
---
This SF.net email is
Would be great if you could attach a zip file containing all files necessary to
reproduce this issue to the bug report ...
Gert
-Original Message-
From: Mark Watts [mailto:[EMAIL PROTECTED]
Sent: Tuesday, January 13, 2004 07:16 PM
To: [EMAIL PROTECTED]
Subject: [nant-dev] Bug #875664
I
I couldn't reproduce the bug, but I have some idea from the analysis of the
*.sln/*.csproj files:
Looks like Uts.NgfEngine.Test.csproj contains a reference with no
HintPath:
Reference
Name = nunit.framework
AssemblyName = nunit.framework
/
that may be causing the problem (this is the
That solved the problem. Removing the reference to nunit.framework in the
project and then adding it back allowed the solution built to complete
successfully. I checked and the HintPath was successfully added to the
reference element in the project file (*.csproj).
I don't know why that one
10 matches
Mail list logo
