On 23/09/2011, at 2:02 AM, Adam Murdoch wrote: >>> 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.
Not sure I made it clear enough. I don't have to specify --no-search-upward when running the test in the Gradle build, but do when running from the IDE. I don't really understand how a different classpath can cause that. -- Luke Daley Principal Engineer, Gradleware http://gradleware.com
