>The only thing I am hearing today is that there is a gap in NAnt's Nunit2
>support. Please forgive my NUnit ignorance. Is the only gate NUnit2
support?
>Can NUnit 2 support be added later via a task?
IMHO, a documented workaround for NUnit2 would be acceptable for the next
release. A point relea
I would like to pose some questions as I am unfamiliar with the scope of the
current release effort. Forgive me if the answers are easily discoverable.
Questions:
What features are we trying to get into the next release?
Which of those features are stable?
Which of those features are not?
Can
Placing the responsibility of getting a release out on the project
admins isn't going to work if the past is any indication of the future
:)
The best way to get a release done is for a number of people to take a
nant-snapshot and QA it to the level that they would feel comfortable to
say that this
As far as I know, most people are using NUnit2. I personally would very much
like to see the release have support or documented procedures for using NAnt
with NUnit 2. One of the things holding back our use of NAnt is that we are
using NUnit2. IMHO using the Command Line Runner would be just fin
>>I am aware of the NUnit to NUnit 2 migration, and have been able to use
>>the latest NAnt and NUnit 2 using the exec task/console runner workaround.
Hi, first-time user - just figured out that 0.7.9 is badly out of date, now
using daily snapshot.
I need to set up an NUnit2 task for my project -
Tomas,
If you see changing NUnit2 as the only solution, it may be less work to
step back from linking to the NUnit2 libraries and use the command line
runner instead.
Reasons:
- The NUnit 2 command line runner has XML/XSLT support built-in.
- Decoupling the NUnit2 task from a specific NUnit2 bu
Kevin Miller wrote:
Yep this is the way it works. We start the thread and someone goes off topic
and the powers that be never make up their mind.
OK valid point. And as one of the project admins I take my share of the
blame for this. Gerry Scott and I discussed a release last time and it
j
Cool- just going it working with the TortoiseCVS version of PLink, that
prompts for the password in a dialog, rather than by stdin/stdout. Now
I'm getting this error. Any ideas?
C:\Temp>cvs -d:ext:mmastrac@nant:/cvsroot/nant co nant
cvs server: Updating nant
cvs server: failed to create lock d
Yep this is the way it works. We start the thread and someone goes off topic
and the powers that be never make up their mind.
OpenSource creedo - Release early and release often.
Kevin Miller
-Original Message-
From: Matthew Mastracci [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, Novembe
I recently found tortoisecvs to be the most painless way to work with
sourceforge from nt/xp. It comes with a customised version of plink to
handle the ssl stuff and is fairly painless to setup.
MG
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Ian
MacL
This is the response I get from cvs. Could be the version of CVS I'm
using, perhaps
Note that I have NAnt set up as a PuTTY connection.
C:\Temp>set CVS_RSH=plink
C:\Temp>cvs -d:ext:mmastrac@nant:/cvsroot/nant co nant
cvs checkout: warning: unrecognized response
`[EMAIL PROTECTED]'
' from
Matthew Mastracci wrote:
While everyone's awake in here - can I ask which branch tag the next
version of NAnt is coming from? I'm sitting on the resx and license
tasks for the moment. As well, I'm still trying to get CVS under
windows to work over PLink to sourceforge so I can actually check
While everyone's awake in here - can I ask which branch tag the next
version of NAnt is coming from? I'm sitting on the resx and license
tasks for the moment. As well, I'm still trying to get CVS under
windows to work over PLink to sourceforge so I can actually check in. :)
Kevin Miller wrot
Everytime this thread is brought up I always have to chime in and say here
here.
So as expected I totally agree. I have 0.7.9.0+ version of NAnt + misc
NAntContrib tasks that I support so that we can actually use NAnt in some
stable fashion. I would rather base my support on a more current ve
Bernard,
> In short, bringing out a new release (0.8.0) is needed.
> Note: A combined NAnt + NAntContrib package Would Be Nice as well, but
> first things first.
>
> I suggest a no-new-features-are-needed approach for this version.
> The question is: What really *needs* to be done before the new
No comments other than just this morning I was thinking the same thing. Let's have a
release!
- Jason
-Original Message-
From: Bernard Vander Beken [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, November 20, 2002 2:39 PM
To: [EMAIL PROTECTED]
Subject: [nant-dev] FAQ: The next NAnt version
Hello,
Every few months since the latest release, someone asked when the latest
NAnt version was going to be replaced. This was no coincidence.
Problems:
- The latest non-CVS NAnt version (0.7.9.0) dates from June 11.
- Too often, problems are reported that were fixed a long time ago or
are rel
17 matches
Mail list logo
