Hi - first of all, thank you for a very nice tool.
I am using NAnt v. 0.8.3.50105 and have the following experiences, which I
hope others might find useful:
* First of all, it seems there's a bug in the way a <references> fileset in
the <csc> target is handled:
<resources basedir="${src.nunit}"
prefix="Com.KapowTech.RoboSuite.Api.Nunit">
<includes name="dotnettest.robotlib" />
<includes name="lib.robotlib" />
</resources>
In the manifest this is transformed to:
.mresource public Com.KapowTech.RoboSuite.Api.Nunit.dotnettest.robotlib
{
}
.mresource public
Com.KapowTech.RoboSuite.Api.Nunit.lib.robotCom.KapowTech.RoboSuite.Api.Nunit
.lib
{
}
It is apparently the presence of 'lib' in the beginning- and end of the
resource that it is confusing matters.
* The <delete> task has an annoying feature of generating an error and
stopping when you try to delete a file or a directory which is not there.
For instance, a typical <clean> target might look like this:
<target name="clean">
<delete dir="${build}" />
</target>
If my build dir is not there (maybe I just did a checkout) NAnt ceases
execution saying that it could not delete the directory because it is not
there. I dont think that NAnt should throw an error in this case. Maybe an
extra attribute like "errorifmissing" could cause NAnt to stop running.
My current workaround for this quirk is:
<target name="clean">
<mkdir dir="${build}" />
<delete dir="${build}" />
</target>
* It is apparently not possible to have NAnt look for a file with properties
in the users home directory, like in Java's Ant. In Java Ant I can include
this line in my script:
<!-- Allow user to override default properties -->
<property file="${user.home}/build.properties"/>
In build.properties I can define various of machine/user specific
properties, like mail address, installation directories of server programs
etc. The properties in this file overwrite the values of the same properties
if these exist in the build file. This feature is extremely useful when
having build files that are in use by more than one developer.
* It would be nice to have some way of testing the .NET Framework version,
and have the build behave accordingly. It would also be nice to be able to
choose which framework version to build a target with (I can see that this
last item is already planned, which is great :-)
Regards
Thomas Koch
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Nant-users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-users
