On 02/05/2012, at 1:21 AM, Russel Winder wrote: > My project compiled and tested fine with 1.0-rc-2 with 1.0-rc-3 I get: > > :compileJava > > FAILURE: Build failed with an exception. > > * What went wrong: > Execution failed for task ':compileJava'. >> invalid source release: 1.7
Do you have a stack trace? And the output of gradle -v? > > This sucks: > > 1. RC-2 worked fine, which means there are changes RC-2 -> RC-3 which > are not bug fixes aimed solely at turning the RC into the final release. The only change between rc-2 and rc-3 was a fix for GRADLE-2258, that touched 2 classes that are only used for compiling Groovy. So, it's unlikely that your problem with compiling Java was introduced in rc-3. The final release will be identical to the most recent RC. We build the final binaries from the same git revision that the RC was built from. The RCs and final releases are all built from a 'release' branch that is isolated from the master branch, and the only changes we make on the release branch are to fix blocker bugs (and sometimes some documentation updates). The first RC is released once all known blockers have been fixed, and represents what we think the final release will be. Subsequent RCs are only done if a blocker is found after the first RC. And so, we think these things can reasonably be called 'release candidates'. -- Adam Murdoch Gradle Co-founder http://www.gradle.org VP of Engineering, Gradleware Inc. - Gradle Training, Support, Consulting http://www.gradleware.com
