Re: [Nant-users] Bug report and feature requests in NAnt v. 0.8.3

[Gert D. <ger...@pa...>]

----- Original Message ----- 
From: "Thomas Michael Koch" <tho...@ka...>
To: <nan...@li...>
Sent: Monday, September 22, 2003 10:29 AM
Subject: [Nant-users] Bug report and feature requests in NAnt v. 0.8.3


> 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.

Can you please file a bug report for this issue
(https://sourceforge.net/tracker/?func=add&group_id=31650&atid=402868) and
add a zip file containing all files necessary to reproduce this problem ?

>
>
>
> * 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.

I agree that we shouldn't generate an error in this case, but there was a
discussion on this topic a while back and I'm pretty sure some people were
against changing this behaviour ...

You could indeed set failonerror to false, but even then a warning is being
output (which, in my opinion, is not necessary) ...

> * 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.

Add all property definitions to a separate build file, and include that file
in your main build file (using the <include> task)

Gert