-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Switch Gradle modules to jCenter? #22
Comments
I'm not sure if this is a problem of this project using Maven Central or if it's more a coincidental problem of IDEA being bad at initialy setting up the repo index? I suppose you'd have had the same issue with any other first project in your IDEA which used Maven Central. |
Yes, it could be a problem with Intellij's Gradle integration, for I had the same problem on an Android Project, which was also developed with Gradle and Intellij. There the Problem disappeared when we replaced mavenCentral() with jcenter(). In the TCG build scripts I noticed that some modules use mavenCentral() and others use jcenter(). Was it intentionally, or by coincidence? I don't know how good and how free of commercial intentions jCenter is, but since it is already used, perhaps it would be good to use only one source of artifacts? |
That was a coincidence. I switched all repos to jcenter() and if the next Travis job survives this, I'll put that on master. Thanks! |
With the default Maven Central repository IntelliJ IDEA downloads a 140 MB repository index file from a slow server. After download is complete, the IDE needs another 20 minutes to index it pushing the CPUs and it still doesn't finish. Perhaps this problem can be avoided by using the jCenter repository for all modules?
The text was updated successfully, but these errors were encountered: