3 ms·
I strongly disagree. Gradle is extremely buggy where it matters the most. For instance, if I cancel a build part-way through and then run it again, gradle assum
by SpaghettiCthulu 2y ago
I strongly disagree. Gradle is extremely buggy where it matters the most. For instance, if I cancel a build part-way through and then run it again, gradle assumes that the in-progress JavaCompile task is completed, and proceeds to generate a Jar file containing resources but no classes. To fix this, I am forced to make useless changes, or clear my entire user-level gradle cache.
- SOLAR_FIELDS 2y agoDoesn’t clean build (or the flag to build the incremental cache again by force) solve this?
- SpaghettiCthulu 2y agoNo, running `gradle clean` only cleans the project-level cache as far as I can tell. It leaves the user-level cache untouched (as far as the issue is concerned). Not sure about that flag you mention though. I'll have to look into that.
- Osiris-Team 2y agoRunning "clean build" should do the trick though, it will delete the ./build directory. Or do you mean the local maven repo?
- SpaghettiCthulu 2y agoNeither. The corrupted cache is in the user-level gradle cache directory, which is untouched by `gradle clean`.