Peter Reilly wrote:
1) Some of the traces seem to imply a bug.
clearly :)
org.apache.tools.ant.taskdefs.Property$PropertyResolver.evaluate(Property.java:110)
at
org.apache.tools.ant.PropertyHelper.getProperty(PropertyHelper.java:787)
- locked <0x00002aaab4013548> (a
org.apache.tools.ant.PropertyHelper)
at
org.apache.tools.ant.PropertyHelper.parseNextProperty(PropertyHelper.java:541)
at
org.apache.tools.ant.PropertyHelper.parseProperties(PropertyHelper.java:502)
at
org.apache.tools.ant.RuntimeConfigurable.maybeConfigure(RuntimeConfigurable.java:390)
The intent of Property.PropertyResolver is I think to remain in
the Property task - the trace seems to imply that it has
escaped from that task.
I think it is looping. There is a per-thread stack to detect this, but
it isnt working. Otherwise the loop wouldnt happen.
This could be some wierd race condition in the JVM itself, which may be
reordering operations in the single thread. Remember, unless your
variable is tagged as volatile, or the block is synchronized, Java can
swap the order of actions. It can even reorder volatile access in Java <1.5
-steve
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
