I
couldn't agree more. We have had a discussion about this and as far as I
remember Tomas Restrepo said the change is only a few lines, which he said he
would do - don't know if he's done it though ...
Enjoy,
Michael Arnoldus
-Original Message-From: [EMAIL PROTECTED]
hmm well the only doc on that I could find is at
http://www.gotdotnet.com/team/libraries/FxCopRules/GlobalizationRules.aspx
which didn't really convince me that its necessary. Are there issues
with the way it is now on on other cultures ?
If it does become necessary then I'd prefer to do it
Hi Mike,
A new version of NUnit is working its way toward beta. It has some
features that people might want, but some of the interfaces have changed.
The NUnit2TestDomain won't work since the interface to RemoteTestRunner has
changed. We probably have to shift back to using NUnits TestDomain.
Command-line purists might argue, but I think an NAnt GUI is a great
idea; I've had several people ask if something like this exists as I've
been evangelizing NAnt in the past few months.
One thought (possibly premature since I haven't actually seen Philip's
contribution yet): If the community
Does the includedirs.../includedirs fileset work?
Since I am invoking Nant from the command line, it will inherit the current
environment. In order to ensure that regardless of a users local workstation
environment, my build works, I use the includedirs.../includedirs
fileset to specify the
Hi Guys,
OK, is it just me, or is NAnt's build/test broken?
During build on my machine, when the unit tests get running, NAnt seems
stuck in an infinite loop spanning instances of NAnt.exe :(
--
Tomas Restrepo
[EMAIL PROTECTED]
---
This
I just did a sync and I'm getting the same thing. The nightly build
seemed to run OK - there have been a bunch of cultureInfo related
changes since then - maybe somthing to do with that.
Ian
Hi Guys,
OK, is it just me, or is NAnt's build/test broken?
During build on my machine, when the unit
Yes, me too. I think it has something to do with changes I made to the
nanttask. It seems to happen on the self-doc target. It is recursive. I've
been thinking about adding a check to make sure that recursive (depth 5)
buildfiles fail by default. This would stop someone from accidentally
creating
I just backed out your change to NAntTest.cs and it builds and tests for
me. I'm going to commit this so that people can build.
Ian
Yes, me too. I think it has something to do with changes I made to the
nanttask. It seems to happen on the self-doc target. It is recursive. I've
been thinking
I just had a thought. The change I made means that the following
includes statement :
includes name=**/* /
will include both files and directories which might break somthing that
is only expecting to get files passed to it.
we could add
filesonly and
directoriesdonly
attributes on the fileset
HI Ian,
I just backed out your change to NAntTest.cs and it builds and tests for
me. I'm going to commit this so that people can build.
Great, thank you :)
I was just able to run all tests, and committed the NUnit2 patch for the
current directory thingy.
--
Tomas Restrepo
[EMAIL PROTECTED]
Tony,
The directories do get added to the Fileset, but under the
Fileset.Includes collection.
Changing the part of ClTask.cs that does the includes to reference
Fileset.Includes instead of Fileset.FileNames fixes that issue. However,
is it the correct, long term fix? Based on what you've stated,
Well, after getting the GUI .NET debugger to work I worked out what was
happening. It was sort of working.
The directories do get added to the Fileset, but under the
Fileset.Includes collection.
Changing the part of ClTask.cs that does the includes to reference
Fileset.Includes instead of
13 matches
Mail list logo
