It does seem that NAntCotrib has a place for non-core tasks. Hopefully the
original goal to open NAntContrib up for more experimental tasks and other
tools.
As Gerry has suggested, to which I agree, the NAnt core will most likely
stabilize and get very little work done on it till the next major ve
Yep, the fileset is case sensitive (because of pattern matching using
regex). There were some discussion about doing the correct thing and using
the case sensitivity of the os/fs, but no code was written (to my
knowledge).
For now you have to be careful about case in your filesets.
I think there
We are feature complete for this release. Er...
um... we are feature done and need to get it out! ;)
Here is what we need to get done, as I see
it.
1--Changelog (We have not been updating this
as checkins happen)
2--Readme (Describing what is in the dist... like
core, nantcontrib tasks,
I agree that a lot of those tasks should be rolled into the main NAnt
project. I think there is still a place for NAntContrib as a place for
user submissions. The idea being that there is a lower barrier of entry
to the contrib project and the best - ie useful to most people tasks get
moved int
Hi Bernard,
<<
If the fork attributes would be removed and set to true internally, and
(only) the NAntContrib tests would be run using the command line runner,
would there be other problems that need to be solved to make the NUnit2
task work for real-world usage?
>>
I think that would work out, y
Tomas,
If the fork attributes would be removed and set to true internally, and
(only) the NAntContrib tests would be run using the command line runner,
would there be other problems that need to be solved to make the NUnit2
task work for real-world usage?
Bernard
> -Original Message-
> F
