ant-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Scott Ellsworth <>
Subject Re: Any way to echo a fileset?
Date Wed, 06 Feb 2002 02:08:29 GMT

Howdy, Eddie.

Thanks much - you found it for me.

On Tuesday, February 5, 2002, at 05:25  PM, Eddie Bernard wrote:

> First thing I would suggest is to:
> 1) Get rid of the "includes" attribute since the <javac> task is smart
> enough to know to pick up *.java -- or,
> 2) Set the "includes" and "excludes" attributes as follows:

This is a degenerate case - I use the same targets for several builds, 
and some do more with their includes/excludes.  For example, other build 
files have includes="org/metagraph/model/*.java" or a list of included 
files to be fed to javac.

Since you have reminded me, though, I am likely going to make my compile 
target a fall-through if nothing is included or excluded for just this 
reason.  Why should it bother hitting the filesystem at all if nothing 
is going to be done?

> I'd also suggest (but not certain that it's even the problem) to use
> "*.java" instead of "**.java".  I believe one asterisk is enough to 
> specify
> the pattern match 'everything with a .java extension'.

This was it.  Making the include **/*.java solved it completely.

The sad thing?  I used the same construct in ten different build files, 
so it looked like something far more subtle.  Nothing would build, and I 
could not figure out why.

Ah well - in the mean time, I solved a number of other inconsistencies, 
and got rid of four needless build properties.

Thanks again,


To unsubscribe, e-mail:   <>
For additional commands, e-mail: <>

View raw message