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 SF.Net email is sponsored by: Oracle 10g
Get certified on the hottest thing ever to hit the market... Oracle 10g.
Take an Oracle 10g class now, and we'll give you the exam FREE.
http://ads.osdn.com/?ad_id=3149&alloc_id=8166&op=click
_______________________________________________
Nant-users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-users
