It was caused because the junit tests were run with Ant 1.6.0 libraries and includeantruntime set to false. This means that even if we are running with Ant 1.7.0, the junit tests were executed against the Ant 1.6.0 libraries.
However, it turned out that this didn't work as I expected. This jvmwatcher stuff has been introduced in Ant 1.7.0. So the <junit> task (Ant 1.7.0) forks a new process and launches the JUnitRunner class (Ant 1.6.0). When the test has ended, the <junit> tasks (Ant 1.7.0) checks the existence of this jvmwatcher file, which has never been created by the forked process (Ant 1.6.0) and thinks the junit tests have crashed. I didn't noticed this problem on my local PC because for some reason Ivy didn't retrieve the correct jars to my lib directory. Only after deleting the Ivy cache, I was able to reproduce the problem. Maarten ----- Original Message ---- From: Gilles Scokart <[EMAIL PROTECTED]> To: [email protected] Sent: Monday, October 8, 2007 2:13:49 PM Subject: Re: Problems with Ant 1.7.0 I aslo had the problem with an ant 1.7 on the IBM jvm 1.5. Taking the latest build.xml and ivy.xml fixed the problem I guess it was because we were using the 1.6 version of the ant core, but were still taking the ant-junit from the ant local installation. Gilles 2007/10/8, Steve Loughran <[EMAIL PROTECTED]>: > > Nascif Abousalh-Neto wrote: > > /home/lib/ivy-snapshot/ivy > java -version > > java version "1.5.0_11" > > Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_11-b03) > > Java HotSpot(TM) Client VM (build 1.5.0_11-b03, mixed mode, sharing) > > > > > Run ant -version. This problem appears to be caused by people with > different versions of ant optional and ant core on their classpath, > possibly if they've been installing versions of ant over yum or apt. > -- Gilles SCOKART ____________________________________________________________________________________ Check out the hottest 2008 models today at Yahoo! Autos. http://autos.yahoo.com/new_cars.html
