ant-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Matt Lyon" <m...@stargus.com>
Subject RE: <support> Vs. FileSet
Date Mon, 29 Oct 2001 14:40:30 GMT
Conor,

I think I have figured out the issue. I was closing the
includes/excludes parameter of the <support> nested element of my
<ejbjar> task incorrectly with a "/>" instead of a ">". In other words,
the errors were caused by my malformed XML. I was closing the <support>
nested element twice, as per the following example:

        <support dir="${build.output.classes.dir}"
                 includes="**/report/**/*.class"
                 excludes="**/*generated*/*,**/*Stub*,**/*Skel*"/>
        </support>

When the <support> nested element is defined as per the example below,
the build succeeds:

        <support dir="${build.output.classes.dir}"
                 includes="**/report/**/*.class"
                 excludes="**/*generated*/*,**/*Stub*,**/*Skel*">
        </support>

Sorry for the false alarm. My bad!

Cheers,

Matt

-----Original Message-----
From: Conor MacNeill [mailto:conor@cortexebusiness.com.au]
Sent: Monday, October 29, 2001 9:22 AM
To: ant-user@jakarta.apache.org
Subject: Re: <support> Vs. FileSet


Matt Lyon wrote:

> Hi,
> 
> I'm a little confused about using the <support> nested element of the
> <ejbjar> task in Ant. It seems to accept a structure using <include>
and
> <exclude> just fine as per the following:
> 
>       <support dir="${build.output.classes.dir}">
>         <include name="**/report/**/*.class"/>
>         <exclude name="**/*generated*/*"/>
>         <exclude name="**/*Stub*"/>
>         <exclude name="**/*Skel*"/>
>       </support>
> 
> However, using a comma-separated list of includes and excludes cause
it
> to bark (as per the following example):
> 
>       <support dir="${build.output.classes.dir}"
>         includes="**/report/**/*.class"
>         excludes="**/*generated*/*,**/*Stub*,**/*Skel*"/>
>       </support>
> 
> Don't all FileSet elements accept both conventions? The <classes>
nested
> element of the <war> task appears to, so why not the <ejbjar>
<support>
> element?
> 


Can I see the "bark" please? <ejbjar> uses a createSupport() method
whereas the others use addClasses(). 


I wouldn't expect that to make a difference, both should be configurable
as regular filesets, so lets see the error to try an figure out what is
hapening


Conor




--
To unsubscribe, e-mail:
<mailto:ant-user-unsubscribe@jakarta.apache.org>
For additional commands, e-mail:
<mailto:ant-user-help@jakarta.apache.org>


--
To unsubscribe, e-mail:   <mailto:ant-user-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:ant-user-help@jakarta.apache.org>


Mime
View raw message