This message was deleted.
# community-support
s
This message was deleted.
v
Run with
-i
and you can see why a specific task is considered out-of-date. But actually copying around
.gradle
and
build
directories is maybe not a good idea and defintely not something that is supported afaik. Maybe you should better leverage a remote build cache to speed up things instead.
👍 1
e
there is a limited set of directories that are supported to be copied: https://docs.gradle.org/current/userguide/dependency_management.html#sub:cache_copy
👍 1
v
Which is neither in
.gradle
nor
build
, but in
GRADLE_USER_HOME
😉
Which typically is
~/.gradle
, but he talked about the one in the project directory
And it would not help to get tasks up-to-date as he wants it, as it is basically just the downloaded dependencies iirc
j
The downloaded dependencies are covered. It's about the tasks now yes
I moved GRADLE_USER_HOME to the project directory, that's why it is there.
v
So you mix the
GRADLE_USER_HOME
.gradle
with the project-local
.gradle
in the same directory? I'm not sure whether that is a good idea. Sounds like it intentionally asks for breakage. 😄
j
Yes it sounded strange when I saw it but it seems to work... apart from the task status then