Well, now you forced me look into this and I think was right. My tests
shows it doesn't matter:

          <includes>
            <anders>**/Bar.java</anders>
            <anders>**/Bar*.java</anders>
          </includes>

Works just fine. It could be that "anders" is some exception, but I
doubt it...:-)

/Anders

On Sat, Aug 18, 2012 at 12:45 AM, Manfred Moser <[email protected]> wrote:
> the child element gets its name automatically and it is derived off the
> collection name. And yes.. afaik it just removes the s.
>
> So it wont work for things like
>
> <mice>
>  <mouse></mouse>
> </mice>
>
> ;-)
>
>
> On Fri, August 17, 2012 3:29 pm, Anders Hammar wrote:
>> I *think* it doesn't matter what you call the child element. But I
>> could be wrong.
>>
>> /Anders
>>
>> On Sat, Aug 18, 2012 at 12:15 AM, KARR, DAVID <[email protected]> wrote:
>>> I'm reading the "Maven Complete Reference" doc from Sonatype.  In the
>>> section on "Multi-valued Mojo Parameters", it has the example of an
>>> "excludes" property, where you specify an "excludes" container element
>>> with child "exclude" elements.  What I don't understand is how it knows
>>> to expect the "exclude" child element.  It's only specifying the name of
>>> the container element, not the child element.  Is it really just
>>> removing the last character from the container element name, to get the
>>> expected name for the child element?
>>>
>>> ---------------------------------------------------------------------
>>> 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]
>>
>
>
> ---------------------------------------------------------------------
> 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]

Reply via email to