ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Matt Benson <>
Subject Re: ResourceCollections
Date Fri, 15 Apr 2005 21:56:13 GMT
--- Martijn Kruithof <> wrote:
> Apart from the variands A and B further below, would
> the following also 
> work?
> <project name="foo" default="bar">
> <resourcecollection id="blah" xmlns="ant:set">
>    <and>
>        <files dir="foo" name="**/*.java"/>
>        <date select="newer" date="2005/04/15"/>
>    </and>
> </resourcecollection>
> </project>
> or would this mean that the resoursecollection must
> be part of set itself?

As I understand it, yes, because the xmlns was
declared on the resourcecollection element.  I am
having a hard time following your exact example here
because I'm not sure how you are imagining the
ResourceCollections to look, while I know what they
look like.  :)

I don't see that the ResourceCollections themselves
need a namespace.  I have modified FileSet and similar
existing types to implement ResourceCollection. 
Really the whole problem goes back to and/or/not, etc.
 "The Princess and the Pea."  Anyway, I translate your
example above as:

<project xmlns:rs="ant:resourceselectors">
  <restrict><!-- ResourceCollection type -->
    <!-- FileCollection aka files has no basedir -->
    <files name="${basedir}/foo/**/*.java" />
    <!-- haven't written this selector yet; here
         mimicked date FileSelector -->
    <rs:date when="after" datetime="2005/04/15"
             pattern="yyyy/MM/dd" />

Does that make sense?


Do you Yahoo!? 
Yahoo! Mail - Find what you need with new enhanced search.

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message