简体   繁体   English

JCenter maven-metadata.xml 没有 Maven Central 的所有模块版本

[英]JCenter maven-metadata.xml doesn't have all module versions from Maven Central

In JCenter net.sourceforge.plantuml:plantuml module doesn't have version 1.2020.15 in maven-metadata.xml .在 JCenter net.sourceforge.plantuml:plantuml模块在maven-metadata.xml中没有1.2020.15版本。

But, in Maven Central this module has this version listed in maven-metadata.xml .但是,在 Maven Central 中,此模块在maven-metadata.xml中列出了此版本。

However, I managed to successfully download net.sourceforge.plantuml:plantuml:1.2020.15 JAR from JCenter .但是,我设法从 JCenter 成功下载net.sourceforge.plantuml:plantuml:1.2020.15 JAR Look like, in this case JCenter redirects me to repo.jfrog.org/artifactory/libs-release-bintray repository, which contains this version.看起来,在这种情况下,JCenter 将我重定向到包含此版本的repo.jfrog.org/artifactory/libs-release-bintray存储库。 And this artifactory repository also has this version listed in maven-metadata.xml .这个工件存储库也有这个版本在maven-metadata.xml中列出。

JCenter documentations says that it's a mirror of Maven Central. JCenter 文档说它是 Maven Central 的镜像。 The question is: shouldn't maven-metadata.xml be fully synchronized?问题是: maven-metadata.xml不应该完全同步吗? It's critical for me, as I use a tool to update my dependencies to latest versions and this tool doesn't update plantuml to the latest version, because this versions isn't listed in maven-metadata.xml in JCenter.这对我来说很重要,因为我使用一个工具将我的依赖项更新到最新版本,并且这个工具不会将 plantuml 更新到最新版本,因为这个版本没有在 JCenter 的maven-metadata.xml中列出。

The Synchronisation of packages in Bintray will happen from JCenter to Maven Central. Bintray 中的包同步将从 JCenter 发生到 Maven Central。 So packages in Maven Central will not always be in JCenter when users request a package that does not exist on JCenter (hence, on-demand), Bintray will try to retrieve it from remote repositories and store it in JCenter.因此,当用户请求 JCenter 上不存在的 package(因此,按需)时,Maven Central 中的包将不会总是在 JCenter 中,Bintray 将尝试从远程存储库中检索它并将其存储在 JCenter 中。

Therefore, JCenter does not duplicate everything under Maven Central (to be reflected in JCenter).因此,JCenter 不会复制 Maven Central 下的所有内容(将在 JCenter 中体现)。 If the package is already linked to JCenter and once the latest version is uploaded to your Bintray account it will be mirrored in JCenter and then you can sync the latest version with Maven Central from your Bintray account.如果 package 已经链接到 JCenter,并且一旦将最新版本上传到您的 Bintray 帐户,它将在 JCenter 中镜像,然后您可以从您的 Bintray 帐户与 Maven Central 同步最新版本。

Please refer the below link for more information on how Maven Central sync works with Bintray: https://www.jfrog.com/confluence/display/BT/Syncing+with+Third-Party+Platforms有关 Maven 中央同步如何与 Bintray 一起使用的更多信息,请参阅以下链接: https://www.jfrog.com/confluence/display/BT/Syncing+with+Third-Party+Platforms

声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

相关问题 Grails版本插件Maven部署不会更新 <latest> 一致地在maven-metadata.xml中标记 - Grails Release Plugin Maven Deployment doesn't update <latest> tag in maven-metadata.xml consistently Artifactory没有缓存maven-metadata.xml文件 - Artifactory is not caching the maven-metadata.xml file 如何在Artifactory中重建maven-metadata.xml? - How to rebuild maven-metadata.xml in Artifactory? maven 尝试从存储库中检索错误的快照版本,因为 maven-metadata.xml - maven tries to retrieve wrong snapshot version from repository because of bad maven-metadata.xml 如何获取artifactory来更新虚拟仓库的maven-metadata.xml? - How to get artifactory to update the maven-metadata.xml for a virtual repo? Maven-metadata.xml没有在工件中自动生成 - maven-metadata.xml not getting auto generated in artifactory Artifactory 检索最新并忽略 maven-metadata.xml - Artifactory retrieve latest and ignore maven-metadata.xml 詹金斯将人工制品部署到Artifactory。 maven-metadata.xml显示的发行版本不正确,并且不显示快照的版本 - Jenkins deploying artifacts to Artifactory. maven-metadata.xml shows incorrect version for release and does not show versions for snapshot Artifactory忽略了maven-metadata.xml文件上的校验和上传 - Artifactory ignores checksum uploads on maven-metadata.xml files Artifactory maven-metadata.xml并与Java API捆绑在一起 - Artifactory maven-metadata.xml and bundles with Java API
 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM