Hi,
Can the folowing patches please be committed
:
- added support for checking a specified framework
is available to the available task
eg. available type="Framework"
resource="mono-0.21" property="mono-0.21.framework.present" /
- updated the xml docs for the available task + use
Dan,
No problem with the cross post. If you can't get an
answer, there is every reason to try again someplace else. :)
You can call NAnt directly (via the Project class),
but NAnt will shell out and call the compiler executables. So, your code will
not call out via the process object, but
Whoops - I just noticed that everything did end up getting applied.
Thanks...
I'm not sure, but the MoveTask looks like it may been to be fixed up as
well. I think a unit test needs to be written to see if the
functionality is correct (the current one succeeds, but I think it only
tests a
The if task has 2 properties to handle what you are
describing. One is "propertyexists" and the other is
"propertytrue".
So, the following is what you want I think. (I have
updated the source so the existence check is done before the true check. It is
an AND operation if both are used.)
if
This patch does a test to see if a pattern should result in a recursive
search. Recursive searches are triggered by either wildcard directory
names or the ** path separator (see the comments for more detail).
The speed increase should be visible for some cases, but you should see
improvements
propertyexists is false when the property does NOT exist OR the property is
false
sounds dangerous to me. Some operation x is supposed run or not, presumably
based on a carefully considered condition. If I forget to set it, I may get
unexpected results.
I agree with the way it's working right now, I didn't know that it was
possible to use an ANd operation using the if task, my mistake sorry.
Thanks,
Gert
- Original Message -
From: Philip Nelson [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Thursday, March 06, 2003 8:55 PM
Subject:
Hi,
I created a patch that will make NAnt.Core
CLSCompliant and that will no longer mae NAnt visible to COM clients (which I
don't think is necessary anyway).
I'm not saying it should be committed, but I think
we should be moving in this direction.
So I hope itwill at least get the
Hi,
This patch exposes the version of the
CurrentFramework and the DefaultFramework as properties.
Can this please be committed ?
Thanks,
Gert
Project.diff
Description: Binary data
Hi,
I forgot to add a few patches, so here's the
complete list of patches.
Thanks,
Gert
FileSet.diff
Description: Binary data
IfTask.diff
Description: Binary data
Log.diff
Description: Binary data
Target.diff
Description: Binary data
TaskContainer.diff
Description: Binary data
Whoops- I keep forgetting the -u :) I can check this stuff in on my end.
Ian MacLean wrote:
Matthew,
I applied your patches to Fileset.cs and directoryscanner.cs as well
as the new copytest.cs. The part of the patch fixing copy and delete
failed to apply against my tree - maybe because the
CLS compliance makes sense but I see no reason to exclude COM clients -
just because you get an fxCop warning.
Ian
Hi,
I created a patch that will make NAnt.Core CLSCompliant and that will no
longer mae NAnt visible to COM clients (which I don't think is necessary
anyway).
I'm not saying
hi all,
I think there's a problem with the ASIS attribute of file sets. Either that
or I have a lingering misunderstanding about what it is supposed to do.
In version 0.8.01, when I use the ASIS file set attribute, incremental
builds don't happen. For example,
csc ...
...
Hi Ian,
Does that mean that you'll commit the patch (with the exception of setting
the ComVisible attribute) ?
Gert
- Original Message -
From: Ian MacLean [EMAIL PROTECTED]
To: Gert Driesen [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Sent: Friday, March 07, 2003 2:37 AM
Subject: Re:
14 matches
Mail list logo
