Catch try task for ant:
-
Hi, Brian:
You are right. After setting the file.encoding, it is working for now. I
agree with you that this is not a good solution for XML replacement.
I am going to try XML Task or XSLT to do this type of work.
Thanks again.
Jerry
From: Brian Agnew <[
I will have it ready for you today.
Testing it
-Original Message-
From: Mark Salter [mailto:[EMAIL PROTECTED]
Sent: Sunday, November 16, 2008 2:47 AM
To: Ant Users List
Subject: Re: AW: AW: token filtering
Rez wrote:
> That's what we really need, more examples. Some
> of the current e
>But I had to find out that properties set inside a are
>not valid outside of said target.
1. Is the target really executed? Maybe an if/unless skips the
execution.
2. If you run a target with a new project instance is created
and the properties
are set there. The calling project hasnt any a
Your XML file specifies the char encoding being used (UTF-8), but I'm
guessing that the replaceregexp task won't understand this, since it's not
XML-aware. So your replacement string may be getting written out using
another encoding - most likely your default environment encoding.
Try setting -Dfi
You are right: Properties are immutable!
Your problem seems to be a different one:
If you do not run the target, the property wont be set.
Make sure you set the property in a task that is called before you use it
elsewhere.
--
Jürgen Knuplesch
-Ursprüngliche Nachricht-
Von: Al
Hi
I'm trying to set a property inside a target. In the definition of ant
properties, it is said that they are immutable. "Beeing set once, they
cannot be reset again". But I had to find out that properties set inside a
are not valid outside of said target.
Is this intended and if so, are there
