>Note, I would try this as a last resoft, I am sure the designers of the
original build.xml had >a reason for the fork="true" attribute and be
careful for un-intented side-effects... also you >may want to search the
file for additonal fork="true" assingments
If this turns out to be the case you could add the jvm attribute to the
junit task to specify the java executable you need to run, i.e.
<junit fork="true" jvm="${clearpath.jvm.name}" ..../>
For more info see the junit task description at
http://ant.apache.org/manual under optional tasks.
****************************************************************
IMPORTANT
The information transmitted is for the use of the intended recipient only and
may contain confidential and/or legally privileged material. Any review,
re-transmission, disclosure dissemination or other use of, or taking of any
action in reliance upon, this information by persons or entities other than the
intended recipient is prohibited and may result in severe penalties. If you
have received this e-mail in error please notify the Privacy Hotline of the
Australian Taxation Office, telephone 13 28 69 and delete all copies of this
transmission together with any attachments.
****************************************************************
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
