Bugzilla? No, according to http://jakarta.apache.org/site/source.html, I was 
supposed to
send them to this list. I have done that twice now. The one I was referring to 
was a few
emails before yours on the list.

What is the logic of the FileSet not handling mappers?  A PatternSet can 
represent a list
of items (say, package names).  A FileSet can not be generated from this unless 
either the
PatternSet or FileSet handle mappers.  Since PatternSet does not allow nested 
PatternSets,
you can not use one PatternSet (package names) for the source of two FileSets 
(.java and
.class) unless the FileSet handles mappers.  By providing mapper capability to 
PatternSet
and FileSet, all tasks immediately have the capability of taking this sort of 
input.

Do we have something, other than the API and Manual, that explain what the 
preferred
design would be?  Doing a grep of the source shows that only about 5 tasks even 
allow
mappers, and PatternSets and FileSets are not very interchangeable.

Thanks,
Malachi

> I do not recall the patches you sent.  Did you post them to Bugzilla?
> What's the number?
> 
> But if you patched FileSet to deal with mappers then something is definitely
> fishy.
> 
>     Erik
> 
> 
> ----- Original Message -----
> From: <[EMAIL PROTECTED]>
> To: "Ant Developers List" <[EMAIL PROTECTED]>; "Ant Developers
> List" <[EMAIL PROTECTED]>
> Sent: Tuesday, February 26, 2002 8:12 PM
> Subject: Re: Patternsets, Filesets, and Mapper
> 
> 
> > Hmmm...  Then perhaps my recent patch submission isn't following the
> correct behavior...
> >
> > Should my recent patch to FileSet and PatternSet instead have patched
> javadoc and jar?
> >
> > Malachi
> >
> > > Mappers aren't nested inside filesets.  Its up to the specific task that
> > > you're working with to provide for mapper capability (like <uptodate>
> for
> > > example).
> > >
> > > This message was more appropriate for the ant-user e-mail list though.
> > >
> > >     Erik
> > >
> >
> >
> >
> > --
> > To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
> >
> >
> 
> 
> --
> To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
> 
> 
> 



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

Reply via email to