On 17/11/2011, at 1:18 AM, Spencer Allain wrote: > In upgrading from one version to another, we've seen extremely strange > behavior in several different ways, but usually only with a project that is > already built in someone's workarea by a previous version of gradle. > > Ensuring that we do a gradle clean in that workspace to remove all of the > build directories seems to avoid the problems. Re-checking out the software > into a clean working area also works nicely.
This is due to http://issues.gradle.org/browse/GRADLE-1501. The workaround is to do a clean after upgrading. > > -Spencer > > From: jean-philippe robichaud <[email protected]> > To: [email protected] > Sent: Wednesday, November 16, 2011 8:08 AM > Subject: Re: [gradle-user] java.lang.NullPointerException right after > starting gradle > > hum, it seems that this was a fluke, maybe because I just upgraded from 1m3. > > I can't reproduce it, but if I even can, I'll post the stack trace. > > Jp > > On Wed, Nov 16, 2011 at 4:39 AM, Luke Daley <[email protected]> wrote: > Can you please provide the full stack trace. > > On 16/11/2011, at 5:25 AM, jean-philippe robichaud wrote: > >> (sent by mistake to [email protected], sorry about that) >> >> Hi, >> >> I just made the switch from the milestone 3 to milestone 5 version. while >> many things are much better (like finding task dependencies, very good!) I >> hit this issue: >> >> if I invoke "gradle abc" in the root directory of my project and then, from >> a different terminal while the abc task still runs, "gradle def" again in >> the root directory, then the 2nd invocation dies very quickly with: >> ------------ >> $gradle -Pdestdir=scratch/qa_1115_4 -x validate publish --info >> Starting Build >> >> FAILURE: Build failed with an exception. >> >> * What went wrong: >> Could not open cache directory >> /home/user/.gradle/caches/1.0-milestone-5/scripts/settings_2buct5j0a42gabdlsv4sp5rjsf/SettingsScript/buildscript. >> Cause: java.lang.NullPointerException (no error message) >> >> * Try: >> Run with --stacktrace option to get the stack trace. Run with --debug option >> to get more log output. >> >> BUILD FAILED >> >> Total time: 1 mins 1.512 secs >> ------------ >> >> As soon as abc is done, this def task starts without problem. >> >> Is there something special I would need to do to make this issue go away? I >> didn't had that with 1m3... >> >> Thanks! >> >> Jp >> > > -- > Luke Daley > Principal Engineer, Gradleware > http://gradleware.com > > > > -- Adam Murdoch Gradle Co-founder http://www.gradle.org VP of Engineering, Gradleware Inc. - Gradle Training, Support, Consulting http://www.gradleware.com
