You get this with ant 1.6.*.
This behavior is kept in ant 1.7.*, but now you will get the message:
Warning: Reference junit.classpath has not been set at runtime, but
was found during
build file parsing, attempting to resolve. Future versions of Ant may support
referencing ids defined in non-exec
Hello,
I use antcontribs "if" and have the following strange effect:
If I define a refid in antfile-passage, that is never reached (using if, else)
ant then
Try to access the refid it has the value that ist set in the not reached code!
Is this correct behaviour?
My Antfile looks like:
dope.fi
Stepan Mishura wrote:
On 11/28/07, Agarkar, M (Milind) <[EMAIL PROTECTED]> wrote:
Thanks Jan.
Any idea about how to trap a PID on-the-fly ? It would be a script to run
automatically.
In snapshot testing we use the next targets to find and kill hung VMs
after a suite run.
that's cute. I'd p
venkata prasad wrote:
Hi All,
I am getting the below error while execting junit task.
Testsuite: BaseServiceCommunicationManagerTest
Tests run: 1, Failures: 0, Errors: 1, Time elapsed: 0 sec
Caused an ERROR
BaseServiceCommunicationManagerTest
java.lang.ClassNotFoundException:
Hi All,
I am getting the below error while execting junit task.
Testsuite: BaseServiceCommunicationManagerTest
Tests run: 1, Failures: 0, Errors: 1, Time elapsed: 0 sec
Caused an ERROR
BaseServiceCommunicationManagerTest
java.lang.ClassNotFoundException: BaseServiceCommunicatio