> Other question: Shouldn't
> 
> cactus.resources.properties.includes = **/**.properties
> cactus.resources.properties.excludes = **bad.properties
> 
> be:
> 
> cactus.resources.properties.includes = **/*.properties
> cactus.resources.properties.excludes = *bad.properties
> 
> ?

true ;) , I don't remember if I want to do **/bad.properties or just 
*bad.properties

> (single star for files - A double star means any number of directories I
> think)

Yes, that the same logic of the paterns in the include/exclude of build 
resources in project.xml.
 
> Also why would the exclude excludes *bad.properties? Would'nt it be good
> enough to write:
> 
> cactus.resources.properties.excludes = bad.properties

I fact *bad.properties illustrate the way to exclude groups of file with 
the same name convention :
*OLD.properties will excludes :
OLD.properties
application-infoOLD.properties
resources-FROLD.properties
...

Nicolas

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to