Hi,
Is it ok to rename the properties that designates a target to execute when
the build fails from "nant.failure" to "nant.onfailure", to have it in sync
with "nant.onsuccess" ?
I know this is a breaking change, so we should document it as such in the
release notes.
In my opinion, changes like
Ian MacLean writes:
> they are building now but not yet passing for me. Missing dependency
> issues. I'll look into it.
Attached is a patch that partially fixes the build issue.
Note that /NAntContrib/Tests/Tasks/TlbImpTaskTest.cs still does not compile
due to an actual dependency on Tests.Nant
Now that we have a cleanly building code base, can someone with CVS write
access create a branch for the 0.8.3 release?
The command to run in the working directory is:
cvs tag -b branch-0-8-3
After running the command, you will still be on the main branch and should
increment the default build nu
Hi Ian,
I just tested this, with my build files which uses vssget, sql and record
task and the vssget and sql task works fines (i prefered when the sql task
wasn't writting every params to the the Console, but that's not really a
problem).
But the record task doesn't work, it simply create an
I was thinking the same thing. There is another reason too. The
ndoc.core.dll that we ship writes to a file c:\test.xml during
processing which breaks for people without c:\ - fortunately not most
windows users but still.
I noticed the speed difference when I ran it against the whole of nant
a
Hi,
I just installed the new NDoc 1.2 beta, and wow am I impressed .. I think
the speed increase for the MSDN documenter is at least x5.
You can now choose whether you want links to .NET SDK 1.0, 1.1 and MSDN
Online, and the MSDN documenter now allows you to generate online (web) docs
...
We sho
