I guess my question was kind of silly, since the wrapper pulls down milestone-4-20110725000027+0200, but how "new" of version features are expected to be used by the latest release of the software?
-Spencer --- On Sat, 8/27/11, Spencer Allain <[email protected]> wrote: From: Spencer Allain <[email protected]> Subject: [gradle-dev] Gradle source bootstrapping To: [email protected] Date: Saturday, August 27, 2011, 2:02 PM This might be intentional, but it seems that in order to build the latest source that an existing milestone-4 build is actually needed (or some snapshot leading up to it) since it uses new functionality within gradle itself. Using milestone-3, I didn't even get through buildSrc before gradle/groovyProject.gradle was referenced and things halted on the use of the new output SourceSetOutput object. I'd rather not hit the penalty of milestone-4 always going out to test every dependency, so is there a recommended snapshot prior to the wharf integration or very current with fixes that should be able to compile the latest code without the performance penalty? -Spencer
