The reason that I can't use
@@path_to_main_properties@@=@@deploy_dir@@\main.properties
is the same reason that my original approach wouldn't
work... the task does not examine/process
the contents of the filterFile.
But going off of what you alluded to, I did come up
with a two-pass approach...
On Wed, 2005-04-20 at 03:40, Ninju Bohra wrote:
> So anybody have any guidance on whether or not
> ${property.name} are resolved in filter
> file?
>
>
> --- Ninju Bohra <[EMAIL PROTECTED]> wrote:
> > Hello all,
> >
> > Just want to make sure that ANT 1.6.2 can NOT do the
> > following (otherwis
So anybody have any guidance on whether or not
${property.name} are resolved in filter
file?
--- Ninju Bohra <[EMAIL PROTECTED]> wrote:
> Hello all,
>
> Just want to make sure that ANT 1.6.2 can NOT do the
> following (otherwise I am doing something wrong...
> which could never be :-))
>
> Wan
Hello all,
Just want to make sure that ANT 1.6.2 can NOT do the
following (otherwise I am doing something wrong...
which could never be :-))
Wanting to replace a bunch of values in a file, so I
created a replaceFilterFile containing all the
token=value entries and using the task I am
able to sea
