That was exactly what I meant. But what if one had an earlier gradle version since earlier in that folder? Can't the build script force a specific version to be used no matter what's in there? (maybe this issue resolves by itself if upgrading to m-6).
I'll try your suggestion in about an hour when I get home. Sent from my iPhone On 22 nov 2011, at 16:00, Stanislav Muhametsin <[email protected]> wrote: > Quoting Marc Grue <[email protected]>: > >> It didn't. In wrapper property, it's m-3, in build.gradle there's a >> gradleVersion pointing to m-2. >> >> When I 'synced' those, either to m-2 or m-3 (having same version in both >> places) it could build. >> >> Sent from my iPhone > > You might have m-2 somewhere in your temporary files. IIRC on Windows at > least, it stores the gradle in C:\Users\<username>\.gradle or something like > that. If it spots any gradle version in there, it will use that. You have to > delete that folder to force it re-download the gradle. > > > _______________________________________________ > qi4j-dev mailing list > [email protected] > http://lists.ops4j.org/mailman/listinfo/qi4j-dev _______________________________________________ qi4j-dev mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/qi4j-dev
