After running the command with `--debug` I found t...
# android
r
After running the command with
--debug
I found that gradle will try to find the dependencies in all repositories. In my project dependencies are scattered in 9 repositories. Gradle spends most of the time looking for most of the dependencies in the irrelevant repositories. Is there a best practice for this?
k
Reordering the repositories should help. Or if you are feeling up to it, you can setup a nexus and use that instead for all the dependencies.
r
Nexus sounds like a good choice then. Thanks!
👍 1
@kingsley is there a quick way to mirror all dependencies of a project and upload them into a Nexus Repository Manager?
Really nice, Nexus Repository Manager just reduces
./gradlew dependencies
from 20 mins to 5s. I'm very happy now, ha ha
👍 2
k
Ah. Great!
k
Care to share what a Nexus Repository is?
k
Copy code
Nexus is a repository manager. It allows you to proxy, collect, and manage your dependencies so that you are not constantly juggling a collection of JARs. It makes it easy to distribute your software.
http://blog.sonatype.com/2010/04/why-nexus-for-the-non-programmer/
🎖️ 1