: Property problem in 1.6.5
FYI, this is a common mistake made; people use antcall incorrectly when
what they needed was the project depends attribute.
Ben
-Original Message-
From: Greg Irvine [mailto:[EMAIL PROTECTED]
Sent: Thursday, April 06, 2006 7:11 PM
To: 'Ant Users List
FYI, this is a common mistake made; people use antcall incorrectly when
what they needed was the project depends attribute.
Ben
-Original Message-
From: Greg Irvine [mailto:[EMAIL PROTECTED]
Sent: Thursday, April 06, 2006 7:11 PM
To: 'Ant Users List'
Subject: Property proble
This is working as designed; ant, antcall
& subant create new contexts and property values set in the context
ARE NOT propegated back to the calling context.
Jeffrey E. (Jeff) Care
[EMAIL PROTECTED]
ed then the jar target. In your example that is
what you accomplished by running "ant update jar".
HTH Bill
-Original Message-
From: Greg Irvine [mailto:[EMAIL PROTECTED]
Sent: Thursday, April 06, 2006 4:17 PM
To: 'Ant Users List'
Subject: RE: Property problem in 1.6.
iginal Message-
From: Greg Irvine [mailto:[EMAIL PROTECTED]
Sent: Friday, 7 April 2006 9:11 AM
To: 'Ant Users List'
Subject: Property problem in 1.6.5
Hi all.
I'm having a problem with property values not existing outside of the target
they're created/set in.
For example (see b
Hi all.
I'm having a problem with property values not existing outside of the target
they're created/set in.
For example (see below), I have a "jar" target that calls an "update"
target. The update calls svn status to populate a property with the current
svn version number and then I echo the pr
