Android的buildscript库。 jcenter VS mavencentral [英] Android buildscript repositories. jcenter VS mavencentral

问题描述

在我最后一次使用Android的工作室，它产生的 .gradle 文件 mavencentral（） buildscript库，而现在有 jcenter（）。

The last time I used Android Studio, it generated .gradle files with mavencentral() buildscript repositories whereas now there's jcenter().

谁能解释与此有关的问题。是否还有其他的回购？我们什么时候切换呢？他们有在项目，模块产生什么影响，库？任何其他生活必需品Android开发？

Could anyone explain the issues connected with this. Are there any other repos? When should we switch them? What impact do they have on projects, modules, libs? Any other essentials for Android developers?

谁负责维护这些回购？

推荐答案

我想知道同样的，我也没有一个明确的答案，但推测它可能是值得分享的内容（小），我​​已经学会了。我发现提的举动从Maven的中央到JCenter <一个href="https://$c$c.google.com/p/android/issues/detail?id=72061&can=1&q=jcenter&colspec=ID%20Type%20Status%20Owner%20Summary%20Stars">within一个问题在谷歌code ，但没有发现的细节究竟何时发生这种情况 - 找不到提及最近发生的变化列表为Android工作室。

I was wondering the same, and I don't have a definitive answer but figured it might be worth sharing what (little) I'd learned. I found mention of the move from Maven Central to JCenter within one issue on Google Code, but didn't spot details about exactly when this happened - couldn't find mention in the recent changes list for Android Studio.

从上JCenter阅读了，它的背后Bintray仓库，从公司JFrog（我以前就遇到过谁，我想这也正是J来自）。根据Bintray博客， Bintray是一个超Maven的中央，因此，如果这是真的不应该有缺失的依赖问题，但我想它要依赖于你在项目中使用什么 - 你总是可以直接检查回购既具有很好的易于搜索的网站。因此，对于谁在维护这些回购，作为最好的，我知道，这是最多的依赖关系的生产者它们的依赖添加到每个回购，最多回购老板只是为了维持服务。

From reading up on JCenter, it is the repository behind Bintray, from the company JFrog (who I've come across before, and I guess that's where the 'J' comes from). According to the Bintray blog, Bintray is a superset of Maven Central, so if that's true there shouldn't be issues with missing dependencies, but I guess it's going to depend on exactly what you're using in your projects - you could always directly check the repos as both have nice easily-searchable websites. So for who maintains these repos, as best I know, it's up to the producers of the dependencies to add their dependencies to each repo, and up to the repo owner just to maintain the service.

在何时切换方面，它是难以奏效的。 AOSP仍在使用Maven的中央，我认为（从寻找在模板中的新Android应用程序），但随后该模板也依然采用了非常古老的摇篮版本（0.4）也是如此。有一个关于他人具有jcenter具有依赖性的问题几个问题，但不是真的有很多报道，这是可能的，谷歌将再次切换到其他回购释放为最终前。如果Maven的中央仍然工作正常，你现在你可以暂缓开关在此之前，特别是如果你是构建大型的商业解决方案。

In terms of when to switch it is difficult to work out. AOSP is still using Maven Central I think (from looking in Templates for New Android Application), but then that template is also still using a very old Gradle version (0.4) as well. There's a couple of issues about others having issues with dependencies from jcenter, but not really a lot reported, and it is possible that Google will switch again to some other repo before releasing AS final. If Maven Central is still working fine for you for now you could hold off switching until then especially if you're building large commercial solutions.

这篇关于Android的buildscript库。 jcenter VS mavencentral的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！