After that sales pitch, I'll definitely investigate the Ant-Contrib
"outofdate". Thanks.
I'm also investigating whether a <depend> selector with a <mapper>
element can do what I'm looking for.
--Wayne
Dominique Devienne wrote:
My bad, I so seldom used uptodate after outofdate came out that I
forgot how much inferior it is to outofdate ;-)
Sounds like Matt's solution's the way to go for pure Ant 1.7+, while
I'd probably use Ant-Contrib's <outofdate> myself, 'cause I'm used to
it, and can nest the tasks to perform directly in the <outofdate>.
--DD
On 7/19/07, Wayne Cannon <[EMAIL PROTECTED]> wrote:
I don't understand how to use <uptodate> for this purpose.
My reading of <uptodate> is that it will set a property if a file is
up-to-date with respect to another file (based on a merge mapper for my
case). I currently use <uptodate> for determining whether certain
operations need to be performed (setting a boolean property), but only
at a very coarse level. My requirement is to select (create a fileset
of) typically 10 to 50 files out of 4000 that have changed recently and
perform an operation with that fileset -- such as creating a zip archive
of all files that have changed since the last zip archive (my reference
file) was created. Other tasks are running file-specific tests on only
those files that have changed (those in the "newer" fileset).
Regards,
--Wayne
Dominique Devienne wrote:
> You can use <uptodate> to select the newer files.
>
> Or Ant-Contrib's <outofdate>, which I find more convenient, since
> avoids having multiple targets, but it adds a dependency. --DD
>
> On 7/19/07, Wayne Cannon <[EMAIL PROTECTED]> wrote:
>> I would like to do the equivalent of a "find -newer reference_file
... |
>> zip ... ", i.e., archiving all files newer than a reference_file. I
>> would like to archive only the files that have changed since the last
>> major archive into a smaller, faster, "delta" archive; much like an
>> incremental backup works.
>>
>> The <date> selector in a <fileset> looks like the logical
solution, but
>> it appears to only use a date-time string and not a reference file to
>> specify the date.
>>
>> Is there a way to use the date-time of a reference file, instead of a
>> string, for the <date> selector?
>> Is there a way to set a property with the date-time of a reference
file
>> so that the property can be passed to a <date> selector?
>> Is there another way to accomplish my goal, such as a way to use
>> <depend> with a single reference file?
>>
>> --Wayne
>>
>>
>> ---------------------------------------------------------------------
>> 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]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
