No, it's not. What you could do is have CC call another target the one it's currently calling, and from that new target use <antcall> to call your regular target. Since properties set during an <antcall> to not propagate to the _parent context_, CC should see it. The drawback is that using the additional <antcall> uses more memory, so CC is likely to die earlier because of an OutOfMemoryError.
Also, did you check CC 2.0.1? CC runs independently of the Ant build, so is now oblivious to this particular problem I think. --DD -----Original Message----- From: Ralph Jocham [mailto:[EMAIL PROTECTED]] Sent: Tuesday, January 21, 2003 4:24 PM To: [EMAIL PROTECTED] Subject: Is it possibe to unset a property??? Hi, in one task I set a property when an error occures. Later I check on that property and depending if it is set or not some actions are taken. This build script is being used from within CruiseCrontrol, which means that it is run again and again without reloading. Which means, once the property is set it is set for good. Is there a way to unset a property?? Thanks, Ralph -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
