This message was deleted.
# community-support
s
This message was deleted.
v
Let me quote https://docs.gradle.org/current/userguide/resolution_rules.html#sec:dependency_substitution_rules:
Adding a dependency substitution rule to a configuration changes the timing of when that configuration is resolved. Instead of being resolved on first use, the configuration is instead resolved when the task graph is being constructed. This can have unexpected consequences if the configuration is being further modified during task execution, or if the configuration relies on modules that are published during execution of another task.
d
Oh, okay, this is expected behavior, I missed it, thank you. Are there any plans to fix it?
v
I have no idea, I'm just a user like you. 🙂 Besides that the question is whether there is something to fix. I guess if you do such substitutions it is a technical necessity to do so. If it is a problem you should probably search for a reported issue or create one if there is none.