This message was deleted.
# community-support
s
This message was deleted.
j
Add a name to that project fixes that warning
s
Aha give it a different name, just so it can figure out that it's its own thing? Also how would I do that, is it just
rootproject.name = "foo"
like normally? I still can't quite figure out what this is for though, so if it has its own unique name, how will this help not break caching?
j
Yes, that line
I think the problem with root is that the name is
""
s
Awesome thanks for helping out! I'll try it as soon as I'm in front of a keyboard again 🙌
v
For included builds that are in a fixed sub folder of the project it is more a false warning. But I'd you e. g. use manual checkout, or Git submodules or whatever and the path can change, then the name of the root project would change too as it is bound to the directory by default and not
""
. Then if you have project accessors enabled, the generated accessor would change too and thus the class path and thus the caching.
👍 2
Just always explicitly specify the root project name as it is good practice anyway and you don't have a problem or warning.
🙌 1
s
Got a much clearer picture on all this now, thank you both! And I no longer get the warning now since I followed your suggestions 😊
👌 1