On 10/9/07, Steve Loughran <[EMAIL PROTECTED]> wrote: > Maarten Coene wrote: > > 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. > > > At the very least, ant should recognise this problem and provide a > warning that mixing ant-junit versions can also be a cause... The trunk of 1.7 does this.
Peter >
