Vincent,
If I understand what you want to do, an easy work around might be to simply
keep all of the properties you want to use as filter tokens in a separate
file and then use the filtersfile attribute of the filter task. I believe
you can dereference properties in a filtersfile using ${} as you normally
would. I seem to remember doing that once upon a time, but you may want to
test it first.
John-Mason Shackelford
Software Developer
NCS Pearson - Measurement Services
2510 North Dodge St.
Iowa City, IA 52245
319-354-9200x6214
[EMAIL PROTECTED]
-----Original Message-----
From: Vincent Massol [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, September 18, 2002 3:45 PM
To: [EMAIL PROTECTED]
Subject: Batch filtering using properties?
Hi,
I'd like to perform batch filtering by adding a whole set of properties as
filter tokens.
My Ant properties all start with a given prefix.
I would like something like the Filter task but instead of a file, I would
need a regexp (or simply a startsWith). For each matching property, it would
add a filter with the name of the property and the value of the property.
I can easily write some ant tasks for that but I wanted to make sure I'm not
missing anything and whether it is not already possible to do this without
resorting to a custom task.
Thanks
-Vincent
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
****************************************************************************
This email may contain confidential material.
If you were not an intended recipient,
Please notify the sender and delete all copies.
We may monitor email to and from our network.
****************************************************************************
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
