On Wed, 2012-05-02 at 06:56 +1000, Adam Murdoch wrote: [...] > > Do you have a stack trace? And the output of gradle -v?
Will get one, but it is a bit more complicated than I thought due to some silliness of some sort on my machines. [...] > 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. Born out by new data. I am installing all released versions from milestone-9 to check. I am absolutely convinced I got a good build with rc-2 prior to committing the wrapper upgrade. However I am no longer able to get a good build with rc-2 -- it complains about the sourceCompatibility = 7 so there is consistency between rc-2 and rc-3 which is good. Although for me it is bad ;-) > 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'. Good process. Now I just have to find the right way of specifying non-default Java level... -- Russel. ============================================================================= Dr Russel Winder t: +44 20 7585 2200 voip: sip:[email protected] 41 Buckmaster Road m: +44 7770 465 077 xmpp: [email protected] London SW11 1EN, UK w: www.russel.org.uk skype: russel_winder
signature.asc
Description: This is a digitally signed message part
