From the what you've said and my observations this has to be that it works but is not suppose to. If that is the case I would request it as an official feature to be supported in later releases because
<resource> <includes name="**/*.properties" /> </resource>
is MUCH more convenient, and elegant, IMHO than
<resource>
<includes>
<include name="**/*.properties" />
</includes>
</resource>Anyway, I'd say any more on the topic is beating a dead horse. Please let me know offline if the Maven team makes a decision on whether this will be supported in future releases of Maven.
[EMAIL PROTECTED] wrote:
"Barnhill William" <[EMAIL PROTECTED]> wrote on 03/12/2003 10:42:53 AM:
I've used this before, and encountered it on other Maven elements. You can have attributes or nested elements. If it's a name attribute then it
can be a comma or space delimited set of patterns. Or you can have a series of nested elements. I would say that one pattern indicates attribute use, >1 indicates nested elements use for clarity and so the patterns can be processed easily via XML technologies.
As a developer of Maven, I'll disagree here, the way xml gets mapped from project.xml to objects in Maven is pretty specific.
Version1 --------
<includes> <include name="*.xsd"/>
Tested with: ------------
<echo>${pom.build.resources[0].includes[0]}</echo>
Results: --------
dgtest: [echo] BUILD SUCCESSFUL
Version2: ---------
<includes> <include>*.xsd</include>
Results: --------
dgtest: [echo] *.xsd BUILD SUCCESSFUL
IMHO, the version1 stuff doesn't work. -- dIon Gillard, Multitask Consulting Blog: http://blogs.codehaus.org/people/dion/
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
