On 18/01/2011, at 6:56 AM, Jeff Brown wrote: > I am troubleshooting some problems we are having with the Grails build > after upgrading to Gradle 0.9. > > What was the default forking behavior for tests on a build back from > something like 0.9-20100118091626+0100?
It was to fork a single test process to run all the tests. This is the same as the default in 0.9. The main difference is that in 0.9-20100118091626+0100, Gradle was still using the junit Ant task, whereas now it drives JUnit directly. This means that the tests will be executed in a different order now. There are some small classpath differences too, in that the Ant runtime has been replaced by a (very, very small) Gradle runtime. > Also, how does that default > behavior relate to options in 0.9 final with respect to > maxParallelForks and forkEvery properties? It is equivalent to maxParallelForks = 1 and forkEvery = 0 (which happen to be the defaults in 0.9). -- Adam Murdoch Gradle Developer http://www.gradle.org CTO, Gradle Inc. - Gradle Training, Support, Consulting http://www.gradle.biz
