> > Fair -- I was mainly just wondering if you (or anyone) knew/remembered off > the top of your head something that had changed in the "architecture" of > our gradle deps on the main branch (since this problem doesn't sem to > affect branch_9x, eventhough it also uses the same version of gradle) >
I've changed the dependency lock checker/ validation from Palantir's to my own but I doubt it's the cause of the problem. More likely it's present on 9x too but doesn't manifest due to different ordering (hash maps, whatever). > Yeah, it's mainly something I do when switching branches -- but also out > of muscle memory. > Incremental builds should work fine even when you're switching branches, actually. I admit that my fool-proof way of restoring pristine state is based on git, not gradle - git clean -xfd . this removes everything though (including the generated gradle.properties) so it may not be for everyone. > Maybe we should add an 'afterEvaluate' hook to complain if people try to > combine "clean" with other tasks on the command line? :) > Nah, better to try to figure out what's going on - I'll file an issue and take a look if I can work it out. Dawid
