[nant-dev] Trying to use the nunit2 task with NAnt version 0.8.3 and NUnit version 2.2.0
Title: Message
I tried using the
nunit2 task and nothing happened. On http://nant.sourceforge.net/nightly/help/tasks/nunit2.htmlI
found a runtime stanza to add to my NAnt.exe.config file. After adding that
stanza I get the output you see below. My tests work fine in the NAnt GUI and in
the NAnt console tool. Is it just a matter of correcting one of the numbers in
the runtime stanza?
thanks,
Eric
Blossom
BUILD FAILED
INTERNAL ERROR
System.TypeLoadException: Could not load type
NUnit.Core.NullListener from assembly nunit.framework, Version=2.2.0.0,
Culture=neutral, PublicKeyToken=96d09a1eb7f44a77. at
NAnt.NUnit2.Tasks.NUnit2Task.ExecuteTask() at
NAnt.Core.Task.Execute() at
NAnt.Core.Target.Execute() at NAnt.Core.Project.Execute(String
targetName) at NAnt.Core.Project.Execute() at
NAnt.Core.Project.Run()
Please send bug report to [EMAIL PROTECTED].
?xml version="1.0" ?
!-- Drives NAnt to build
Bruce Eric Blossom - November, 2004--
project name="bruce"
default="test" descriptionMockup of a Workflow
Wizard/description property
name="nant.settings.currentframework" value="net-1.1"/
property name="debug" value="true" / property
name="project.name" value="Bruce" / property
name="project.version" value="0.1" / property name="build.dir"
value="build" / property name="ourpkg"
value="com/affymetrix/workflow_wizard_mockup" / property
name="nunitf.dir"
value="C:/Program Files/NUnit
2.2/bin"
/ echo message="Using '${nant.settings.currentframework}'
Framework"/
target
name="test"
description="Unit Tests for
Bruce"
depends="compile-test"
echo message="testing..."
/ nunit2
verbose="true" formatter type="Plain"
/
test assemblies
basedir="test/${ourpkg}"
includes name="Test*.dll"
/
/assemblies
/test /nunit2
/target
target name="compile-test"
depends="compile" verbose="true" csc
target="library" output="${build.dir}/Form1Test.dll"
debug="${debug}" sources
basedir="test/${ourpkg}"
includes name="*.cs" /
/sources
references includes
name="${build.dir}/WorkFlowWizard.exe"
/ includes
name="${nunitf.dir}/nunit.framework.dll" /
/references /csc
/target
target name="compile"
description="Compilation" depends="prep" csc
target="exe" output="${build.dir}/WorkFlowWizard.exe"
debug="${debug}" sources
basedir="src/${ourpkg}"
includes name="*.cs" /
/sources /csc
/target
target
name="prep" mkdir dir="${build.dir}"
/ /target
target name="clean" description="remove
all generated files" delete
file="${build.dir}/*.exe" failonerror="false" /
delete file="${build.dir}/*.pdb" failonerror="false"
/ delete dir="${build.dir}" failonerror="false"
/ /target
/project
Re: [Ccnet-user] RE: [nant-dev] SVN+latest NAnt in automated environment like CCNe t
It sounds like NAnt is now doing what VS does so that sounds like the
right thing to me.
Files that are *created* (and not editted) by a build process should
be marked as 'ignore', and I believe that should fix the problem
(certainly that works when using CVS). Furthermore, we're used to
automated builds having a 'clean' task - if necessary they could have
a 'teardown' task to remove any temporary artifacts, but I think a
combination of ignored files/directories and just a 'clean' build task
is fine.
Mike
On Fri, 5 Nov 2004 15:41:34 +0100, Nicklas Norling
[EMAIL PROTECTED] wrote:
To me this is a bug in subversion. One of the most obvious use-cases aren't
supported; automated builds.
I'd love to see many of Subversions commands have a --force parameter so
that
I didn't have to work around it.
I do howevery think that if a task is supposed to do what VS does, then it
should
do so. Otherwise one would have to invent different hacks for different
compilers.
Remember that users of VS automatically ends up with these bin and obj
folders and
have to deal with them as well.
/Nicke
-Original Message-
From: Martin Aliger [mailto:[EMAIL PROTECTED]
Sent: den 5 november 2004 10:40
To: [EMAIL PROTECTED]; ! nant
Subject: [nant-dev] SVN+latest NAnt in automated environment like CCNet
Hi all,
just FYI latest NAnt change behaviour of build process little and now
solution task produce obj folder under project directory. This match
VS.NET behaviour what is good. What is bad it could broke automated builds!
I notice that when some user want to delete entire project under SVN. Since
local repository is modified by NAnt build process (new subdir), svn is
unable to delete project and fail with message
exec program=c:\program files\subversion\bin\svn.exe commandline=update
--non-interactive ${build.dir}/ External Program Failed: c:\program
files\subversion\bin\svn.exe (return
code was 1)
svn: Won't delete locally modified directory c:/ccnet/foo'
svn: Left locally modified or unversioned files
Even Revert+Update do not help (revert do not touch unversioned files).
Deleting all obj folders (what is only solution I see) could be quite
performance hit for very large projects. And, of course, more work, more
complex .build script etc. I'd say I liked old behaviour more...
Martin
---
This SF.Net email is sponsored by:
Sybase ASE Linux Express Edition - download now for FREE
LinuxWorld Reader's Choice Award Winner for best database on Linux.
http://ads.osdn.com/?ad_id=5588alloc_id=12065op=click
___
Ccnet-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/ccnet-user
--
mike roberts | http://mikeroberts.thoughtworks.net/ |
http://www.thoughtworks.com/
---
This SF.Net email is sponsored by:
Sybase ASE Linux Express Edition - download now for FREE
LinuxWorld Reader's Choice Award Winner for best database on Linux.
http://ads.osdn.com/?ad_id=5588alloc_id=12065op=click
___
nant-developers mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-developers
Re: [nant-dev] Trying to use the nunit2 task with NAnt version 0.8.3 and NUnit version 2.2.0
Hi Eric.
I'd like to point out that you are using documentation for the latest
nightly for nunit2 task while you
are executing it with a pre-historic version of nant.
I think you should use the 0.8.3 docs. Don't even think nunit2 existed then.
Also, i'm not sure if you are aware of it but a huge amount of fixes in
all areas of Nant has been
included since 0.84 was released, I can't even begin to imagine how many
bugs 0.83 would have.
If I where you I'd use the latest nightly and give that a try. If it
still won't work then you would be in
a much better position to get help on the list.
/Nicke
Blossom, Eric wrote:
I tried using the nunit2 task and nothing happened. On
http://nant.sourceforge.net/nightly/help/tasks/nunit2.html I found a
runtime stanza to add to my NAnt.exe.config file. After adding that
stanza I get the output you see below. My tests work fine in the NAnt
GUI and in the NAnt console tool. Is it just a matter of correcting
one of the numbers in the runtime stanza?
thanks,
Eric Blossom
BUILD FAILED
INTERNAL ERROR
System.TypeLoadException: Could not load type NUnit.Core.NullListener
from assembly nunit.framework, Version=2.2.0.0, Culture=neutral,
PublicKeyToken=96d09a1eb7f44a77.
at NAnt.NUnit2.Tasks.NUnit2Task.ExecuteTask()
at NAnt.Core.Task.Execute()
at NAnt.Core.Target.Execute()
at NAnt.Core.Project.Execute(String targetName)
at NAnt.Core.Project.Execute()
at NAnt.Core.Project.Run()
Please send bug report to [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED].
?xml version=1.0 ?
!--
Drives NAnt to build Bruce
Eric Blossom - November, 2004
--
project name=bruce default=test
descriptionMockup of a Workflow Wizard/description
property name=nant.settings.currentframework value=net-1.1/
property name=debug value=true /
property name=project.name value=Bruce /
property name=project.version value=0.1 /
property name=build.dir value=build /
property name=ourpkg value=com/affymetrix/workflow_wizard_mockup /
property name=nunitf.dir
value=C:/Program Files/NUnit 2.2/bin
/
echo message=Using '${nant.settings.currentframework}' Framework/
target name=test
description=Unit Tests for Bruce
depends=compile-test
echo message=testing... /
nunit2 verbose=true
formatter type=Plain /
test
assemblies basedir=test/${ourpkg}
includes name=Test*.dll /
/assemblies
/test
/nunit2
/target
target name=compile-test depends=compile verbose=true
csc target=library output=${build.dir}/Form1Test.dll
debug=${debug}
sources basedir=test/${ourpkg}
includes name=*.cs /
/sources
references
includes name=${build.dir}/WorkFlowWizard.exe /
includes name=${nunitf.dir}/nunit.framework.dll /
/references
/csc
/target
target name=compile description=Compilation depends=prep
csc target=exe output=${build.dir}/WorkFlowWizard.exe
debug=${debug}
sources basedir=src/${ourpkg}
includes name=*.cs /
/sources
/csc
/target
target name=prep
mkdir dir=${build.dir} /
/target
target name=clean description=remove all generated files
delete file=${build.dir}/*.exe failonerror=false /
delete file=${build.dir}/*.pdb failonerror=false /
delete dir=${build.dir} failonerror=false /
/target
/project
---
This SF.Net email is sponsored by:
Sybase ASE Linux Express Edition - download now for FREE
LinuxWorld Reader's Choice Award Winner for best database on Linux.
http://ads.osdn.com/?ad_id=5588alloc_id=12065op=click
___
nant-developers mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-developers
