If not, is there a location where I can delete it manually?

# kapt

[agrosner]

If not, is there a location where I can delete it manually?

[sujin]

Only kapt build cache? while keeping the rest as it is?

[agrosner]

Well it keeps resurfacing generated classes that I moved to another package. Disabling gradle build cache didn't change that they resurface

[yan]

^ @h0tk3y

[agrosner]

any news? Its annoying on other laptops even clearing the gradle build class recreates some outdated generated files

[agrosner]

not sure where I can actually clear it

[agrosner]

@h0tk3y

[h0tk3y]

Sorry for taking so long. I believe you can delete the Gradle build cache located in ~/.gradle/cache/build-cache-1 (or something similar), though if the classes keep appearing with the wrong package names even with caching disabled, it might mean there's a problem somewhere else, e.g. in incremental compilation. Does this happen in a clean build with caching enabled? Anyway, an issue like this is worth investigating deeper, so it will be great if you report it to the issue tracker and provide more details so that we can try to reproduce it.

[agrosner]

sure I can report it. I run ./gradlew cleanBuildCache, also clear out the build/ dir of the offending directory. I will try that in the gradle cache

[agrosner]

I will test removing the directory and then if it fails, report my steps.

[agrosner]

and yes it happens in a clean build with caching enabled. I can try disabling it

[agrosner]

disabling cache, clearing it, building works. enabling cache +building again works too. shouldnt kapt clear its build cache during the cleanBuildCache task?

[h0tk3y]

AFAIK, cleanBuildCache relates to Android Build Cache, which is a different thing from Gradle Build Cache.