On 23/09/2011, at 8:45 AM, Luke Daley wrote: > > On 22/09/2011, at 9:58 PM, Adam Murdoch wrote: > >> On 23/09/2011, at 2:52 AM, Luke Daley wrote: >> >>> I am trying to debug the test I just wrote… >>> >>> https://github.com/gradle/gradle/blob/master/subprojects/launcher/src/integTest/groovy/org/gradle/launcher/daemon/DaemonDisappearingProcessSpec.groovy >> >> You need to make sure that your test build either has a settings.gradle or >> runs with --no-search-upward. Otherwise, it searches up and finds Gradle's >> own settings.gradle, and tries to execute it. Which means it first needs to >> build buildSrc. Which means it needs to invalidate what's already there. > > Why does that only happen in the IDE?
Not entirely sure. The IDE and the int tests do run with different classpaths, and so the daemon will be launched with potentially different classpaths, which means different stuff will be visible (or not) to the build. The stacktrace might have some clues. -- Adam Murdoch Gradle Co-founder http://www.gradle.org VP of Engineering, Gradleware Inc. - Gradle Training, Support, Consulting http://www.gradleware.com
