PM
To: user@ant.apache.org
Subject: RE: properties handling problem
Hi,
both tasks, and only works with ant-contrib 0.6 - i
suppose...
1.0b2 is without the for-task...
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For
s the unset attribute.
see http://ant-contrib.sourceforge.net/tasks/tasks/index.html
Property Tasks / Variable
Regards, Gilbert
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Monday, July 31, 2006 4:21 PM
To: user@ant.apache.org
Subject: RE: properties handli
Ant _does_ expand macro parameters the way you want, however (this
discrepancy is unintuitive and baffling to me, but that's another
story). So, you could make the part that checks availability a
macrodef, passing in ${hostname} and ${num} as arguments. You will then
be able to reference [EMA
-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Monday, July 31, 2006 4:21 PM
To: user@ant.apache.org
Subject: RE: properties handling problem
Hi,
first, thanks for your help!!
I tried to implement the pfunctions - lib.. but not so successful..
I think the solution with ant-contrib and the
Recursive property expansion can be emulated using a .
Processing [EMAIL PROTECTED] (IP: [EMAIL PROTECTED])
...
If you have in your properties file:
host_1_name = foo
host_1_ip = 255.255.255.0
Calling
Will display: Processing foo (IP: 255.255.255.0). --DD
On 7/31/06, [EMAIL PRO
ilto:[EMAIL PROTECTED]
Sent: maandag 31 juli 2006 16:21
To: user@ant.apache.org
Subject: RE: properties handling problem
Hi,
first, thanks for your help!!
I tried to implement the pfunctions - lib.. but not so successful..
I think the solution with ant-contrib and the 'for' - iteration i
Hi,
first, thanks for your help!!
I tried to implement the pfunctions - lib.. but not so successful..
I think the solution with ant-contrib and the 'for' - iteration is good...
But following problem embarrass me...
BUILD FAILED
C:\workspace\Synchro - Tool\Ant - Tests\build.xml:24: The type do
Second suggestion =
i think your problem is, that properties are immutable once set
here's a workaround with from antcontrib :
Filepath === @{file}
Filename === ${filename}
the property file is automatically overwritten for every loop, but
the property filename
Hi,
Don't know if that is what you want, but if needed
properties may always be set or overwritten via script , f.e.
ant.project.setProperty("FOO","schwall");
Reset Nr.1 via Groovy >>> ${FOO}
You have allway
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Monday, July 31, 2006 11:06 AM
To: user@ant.apache.org
Subject: properties handling problem
Hi,
this is Code for deliver files to different systems with a pre-check...
I'll iterate with der f
I believe ant dies not support the parsing of inner variables (property
expansion), so you will have to make a combination with a
task and loading the resulting property file after that.
There are some ant extensions that make it possible, but they are in
development. http://www.efanomars.net/
11 matches
Mail list logo