There’s a detachedConfiguration(dependencies) method on the ConfigurationContainer. These are often used by plugins that internally need to resolve a dependency to do their work. As these configurations are an implementation detail of something in the build, they’re not added to ConfigurationContainer like the ones you’re expected to add dependencies to for your application.
Thanks a tonne for answering that, So that means I need to revisit the plugins that have been added to my gradle? Also is it possible to exclude this, Cause as you see these steps take a lot of time during my first gradle build. It takes like an hour for resolving each of the detachedConfiguration and I can’t figure out why.
You can’t disable resolution of the detached configurations. These are hard dependencies for the code that uses them. If you don’t need what is creating them and configuring them, removing them is the answer. However, even the resolution of your runtimeClasspath seems ridiculously long. Are you in an extremely bandwidth limited environment?
I get your point. The organisation has good bandwidth, although I’d assume it’s something to do with the proxy. I tried adding proxy to the IDE but it still takes time? Would it make sense if I post my build.gradle file here and see if I messed up something with the dependency plugins?
The more details you can provide to help with understanding what you have and what could impact what you’re seeing, the better. Although, it seems most likely we will only be able confirm what it’s not as reproducing your environment at the organization won’t be possible.