This message was deleted.
# configuration-cache
s
This message was deleted.
r
does it change what happens at configuration time? I need to check.
t
I was trying to debug something during the configuration phase. but because I'd already run that task without the debug flag, configuration was skipped!
r
Would you expect
org.gradle.debug
to always invalidate the cache?
t
I think this was just one of those things that was surprising in the moment, but upon reflection (and conversation; thanks!) makes sense. It reminds me of when people complain about
test
not re-running their tests because Gradle has determined there's no reason to
r
Got it