I’m noticing that for some projects, gradle will resolve dependencies during the configuration step. This is perfectly normal for plugins and other deps on the gradle classpath. The problem is that is very easy to accidentally tell gradle to resolve compile and build dependencies during configuration, before any compile or build tasks are even executed.
How do you use configuration objects in copy, zip, and jar tasks so that gradle does not resolve them early?
I think this behavior should also throw a warning to the user because 99% of the time you do not want to download dependencies that will not even be required for the execution tasks. Another option would be to have runtime switch to break the build if a project configuration is being resolved in the configuration step. Thoughts?