Scott,

I think you nailed it.  The addition of a "failonmissing" attribute
would be quite helpful.  

If you try to build using the VS.NET IDE, the build will fail if a file
is missing.  In an automated build process I want to be able to
implement the same behavior.  This allows the build to be more
consistent between the IDE and NANT.  I've seen from practice that when
there are subtle differences between 2 build environments, many hours
can be lost in tracking down an issue.

Thanks,

Bruce

-----Original Message-----
From: Scott Hernandez [mailto:[EMAIL PROTECTED] 
Sent: Saturday, May 01, 2004 11:15 AM
To: Gert Driesen
Cc: Hearn, Bruce; [EMAIL PROTECTED]
Subject: Re: [Nant-users] RE: problem with ASIS attribute on source file
list in CSC task

It would definitely be a nice feature to say that a certain <includes/>
is
required and should throw an error if no match on the filesystem is
found.
But no, this should not be the default behavior. The problem in the past
has
been with wildcard expressions and the fileset implementation not easily
allowing for a check that a wildcard statement results in filesystem
hit.
Adding the 'failonempty' attribute to the <fileset/> seems like a
stop-gap
measure to ensure this kind of checking.

I think this is where Bruce is coming from. Bruce?

Here is an example:

<copy>
    <fileset>
        <includes name="bin/myprogram.exe" failonmissing="true"/>
        <includes name="bin/resources/**/*" />
    </fileset>
<copy>

----- Original Message ----- 
From: "Gert Driesen" <[EMAIL PROTECTED]>
> > ----- Original Message ----- 
> > From: "Hearn, Bruce" <[EMAIL PROTECTED]>
> > Hi Gert,
> > a) if a non-existent file is included in the source list, it
compiles
> > anyway without error or warning.
>
> The sources to compile are specific using a fileset, which actually
uses
> pattern matching and scanning to determine the matching files. A file
that
> doesn't exist will therefor not be part of the resulting matches.  I
don't
> think we will be changing this.  Ian, Scott : what do you think ?
Should
we
> throw a build error when the includes name does not contain a wildcard
> pattern, and does not exist ?



This message was scanned for viruses!!




-------------------------------------------------------
This SF.Net email is sponsored by Sleepycat Software
Learn developer strategies Cisco, Motorola, Ericsson & Lucent use to deliver
higher performing products faster, at low TCO.
http://www.sleepycat.com/telcomwpreg.php?From=osdnemail3
_______________________________________________
Nant-users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-users

Reply via email to