Thanks for reporting the problem. I think this is not a regression in the latest versions since I can reproduce the problem with all versions 2.11, 2.12, 2.13 if the .gradle directory is removed in the build directory between invocations. I guess the only way to get around the problem is to run clean whenever the Gradle version gets upgraded. There might be a nice way to automate this.