: 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 problem in 1.6.5
H
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.
Ok. I've progressed slightly on this. It seems a property set in one
target isn't returned to the calling target, however, if I call the targets
separately, it works.
e.g. "ant update jar", rather than "ant jar" and have jar call update.
Hmm...
-Original Message-
From: Greg Irvine
