解决Could not transfer metadata org.apache.maven.plugins:maven

最新推荐文章于 2025-09-10 10:32:49 发布
原创 最新推荐文章于 2025-09-10 10:32:49 发布 · 9.3k 阅读 · 12 ·
CC 4.0 BY-SA版权
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。

解决Could not transfer metadata org.apache.maven.plugins:maven-archetype-plugin/maven-metadata.xml from aliyun

今天构建Maven项目，创建空工程添加模块，使用javase模板。quickstart这个模板，但是添加模块不成功报了一个这样的错误
在这里插入图片描述
这里显示的意思是访问不到阿里的镜像服务器，一些模板需要依赖的插件就下载不下来，下载不下来就无法使用，最后找到解决方案

这个是ssl证书出现问题，只要在idea的Maven设置VM Opation这个位置加上：
-Dmaven.wagon.http.ssl.insecure=true -Dmaven.wagon.http.ssl.allowall=true -Dmaven.wagon.http.ssl.ignore.validity.dates=true
在这里插入图片描述
在这里插入图片描述
在这里插入图片描述

这样就解决了问题，注意我们需要在settings中配置一次，还需要在Other Settings 中进行配置一次
解释一下：settings配置表示这个工程中设置这样的效果，Other Settings配置的是其他工程也设置这样的效果。这样就达到了一劳永逸

参考大佬指示：https://www.zhihu.com/question/350864269/answer/993425872

Maven问题：Downloading from central: https://repo1.maven.org/maven2/org/apache/maven/plugins/maven-a
01-07
Downloading from central: https://repo1.maven.org/maven2/org/apache/maven/plugins/maven-archetype-plugin/maven-metadata.xml 很奇怪，我的maven仓库配置了私有库，，并且在maven setting.xml中配置了mirror...
解决 Maven 500 错误：无法传输 maven-metadata.xml 文件
qq_36291550的博客
04-15 1359
Maven 仓库中的文件是管理版本信息和元数据的关键文件。当出现错误时，通常与元数据文件的损坏或缺失有关。通过删除旧的元数据文件、重建元数据、检查日志和调整仓库顺序，可以有效解决该问题。希望这些步骤能够帮助你顺利恢复 Maven 构建过程中的正常工作。
解决Could not transfer metadata org.apache.maven.plugins:maven-archetype-plugin/maven-metadata.xml fro
qq_36371162的博客
07-18 2万+
昨天在新建maven工程的时候，出现了一个之前没遇到的问题，具体问题截图如下： 错误显示的主要意思是说访问不到阿里的镜像服务器，然后一些依赖的包就下载不下来。搜索到的解决方案主要是说maven里的settings文件中没有配置阿里的镜像服务器，也有的说是网速的问题，毕竟公司的网速太感人了。我觉得这两个地方都有可能出现问题。但是经过测试，问题依然没有解决。 如果大家也遇到这种问题，接下来就给大家解决： 这个是证书出现问题，只要在idea的这个位置加上：-Dmaven.wagon.http.ssl.insec
[WARNING] Could not transfer metadata maven-metadata.xml from/to maven-default-http-blocker
yuchenxideyu的博客
09-10 303
解决Maven打包报错"Blocked mirror for repositories"的两种方案： 降级Maven至3.6.3版本（旧版本未限制HTTP仓库） 在settings.xml文件中添加配置覆盖默认的HTTP拦截器（适合继续使用Maven 3.9.9的情况） 该问题是由于Maven 3.8.1+版本默认阻止HTTP仓库访问导致的，通过修改配置或降级版本均可解决。
解决Could not transfer metadata org.apache.maven.plugins:maven-archetype-plugin/..
weixin_51735258的博客
04-18 2万+
使用idea创建Springweb文件时， 报：Could not transfer metadata org.apache.maven.plugins:maven-archetype-plugin/maven-metadata.xml from/to alimaven (http://maven.aliyun.com/nexus/content/repositories/central/): Transfer failed for http://maven.aliyun.com/nexus/conten.
阿里云Maven
qq_25974013的博客
12-11 251
<mirror> <id>alimaven</id> <name>aliyun maven</name> <url>http://maven.aliyun.com/nexus/content/groups/public/</url> <mirrorOf>central</mirrorOf> </mirror> <mirror> <.
IDEA新建web项目时报 Could not transfer metadata org.apache.maven.plugins:maven-archetype-plugin/maven-meta
qq_62761962的博客
09-09 1799
IDEA新建web项目时报 Could not transfer metadata org.apache.maven.plugins:maven-archetype-plugin/maven-meta & Failed to create parent directories for tracking file D:\Program Files\Java\apache-maven-3.8.6-bin\a...
Maven更新失败，Cannot resolve plugin org.apache.maven.plugins:maven-compiler-plugin:3.1
01-20
在apache-maven-3.5.2/conf/setting.xml中加入以下配置即可解决 alimaven aliyun maven http://maven.aliyun.com/nexus/content/repositories/central/ central junit junit Address/ ...
mvn help:effective-settings 验证后输出 Could not transfer metadata org.apache.maven.plugins/maven-metadata.xml from/to huawei-product-maven-plugin
10-18
"Could not transfer metadata org.apache.maven.plugins/maven-metadata.xml from/to huawei-product-maven-plugin" 这个错误表明 Maven 在尝试从名为 "huawei-product-maven-plugin" 的仓库（或插件仓库）中获取...
[WARNING] [WARNING] Some problems were encountered while building the effective settings [WARNING] Unrecognised tag: 'mirror' (position: START_TAG seen ...<!-- \u963f\u91cc\u4e91\u955c\u50cf -->\n <mirror>... @162:11) @ D:\JavaMaven\apache-maven-3.9.11\conf\settings.xml, line 162, column 11 [WARNING] [INFO] Scanning for projects... Downloading from central: https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-clean-plugin/3.2.0/maven-clean-plugin-3.2.0.pom [WARNING] Failed to retrieve plugin descriptor for org.apache.maven.plugins:maven-clean-plugin:3.2.0: Plugin org.apache.maven.plugins:maven-clean-plugin:3.2.0 or one of its dependencies could not be resolved: The following artifacts could not be resolved: org.apache.maven.plugins:maven-clean-plugin:pom:3.2.0 (absent): Could not transfer artifact org.apache.maven.plugins:maven-clean-plugin:pom:3.2.0 from/to central (https://repo.maven.apache.org/maven2): sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target Downloading from central: https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-install-plugin/3.1.2/maven-install-plugin-3.1.2.pom [WARNING] Failed to retrieve plugin descriptor for org.apache.maven.plugins:maven-install-plugin:3.1.2: Plugin org.apache.maven.plugins:maven-install-plugin:3.1.2 or one of its dependencies could not be resolved: The following artifacts could not be resolved: org.apache.maven.plugins:maven-install-plugin:pom:3.1.2 (absent): Could not transfer artifact org.apache.maven.plugins:maven-install-plugin:pom:3.1.2 from/to central (https://repo.maven.apache.org/maven2): sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target Downloading from central: https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-deploy-plugin/3.1.2/maven-deploy-plugin-3.1.2.pom [WARNING] Failed to retrieve plugin descriptor for org.apache.maven.plugins:maven-deploy-plugin:3.1.2: Plugin org.apache.maven.plugins:maven-deploy-plugin:3.1.2 or one of its dependencies could not be resolved: The following artifacts could not be resolved: org.apache.maven.plugins:maven-deploy-plugin:pom:3.1.2 (absent): Could not transfer artifact org.apache.maven.plugins:maven-deploy-plugin:pom:3.1.2 from/to central (https://repo.maven.apache.org/maven2): sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target Downloading from central: https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-site-plugin/3.12.1/maven-site-plugin-3.12.1.pom [WARNING] Failed to retrieve plugin descriptor for org.apache.maven.plugins:maven-site-plugin:3.12.1: Plugin org.apache.maven.plugins:maven-site-plugin:3.12.1 or one of its dependencies could not be resolved: The following artifacts could not be resolved: org.apache.maven.plugins:maven-site-plugin:pom:3.12.1 (absent): Could not transfer artifact org.apache.maven.plugins:maven-site-plugin:pom:3.12.1 from/to central (https://repo.maven.apache.org/maven2): sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target Downloading from central: https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-antrun-plugin/3.1.0/maven-antrun-plugin-3.1.0.pom [WARNING] Failed to retrieve plugin descriptor for org.apache.maven.plugins:maven-antrun-plugin:3.1.0: Plugin org.apache.maven.plugins:maven-antrun-plugin:3.1.0 or one of its dependencies could not be resolved: The following artifacts could not be resolved: org.apache.maven.plugins:maven-antrun-plugin:pom:3.1.0 (absent): Could not transfer artifact org.apache.maven.plugins:maven-antrun-plugin:pom:3.1.0 from/to central (https://repo.maven.apache.org/maven2): sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target Downloading from central: https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-assembly-plugin/3.7.1/maven-assembly-plugin-3.7.1.pom [WARNING] Failed to retrieve plugin descriptor for org.apache.maven.plugins:maven-assembly-plugin:3.7.1: Plugin org.apache.maven.plugins:maven-assembly-plugin:3.7.1 or one of its dependencies could not be resolved: The following artifacts could not be resolved: org.apache.maven.plugins:maven-assembly-plugin:pom:3.7.1 (absent): Could not transfer artifact org.apache.maven.plugins:maven-assembly-plugin:pom:3.7.1 from/to central (https://repo.maven.apache.org/maven2): sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target Downloading from central: https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-dependency-plugin/3.7.0/maven-dependency-plugin-3.7.0.pom [WARNING] Failed to retrieve plugin descriptor for org.apache.maven.plugins:maven-dependency-plugin:3.7.0: Plugin org.apache.maven.plugins:maven-dependency-plugin:3.7.0 or one of its dependencies could not be resolved: The following artifacts could not be resolved: org.apache.maven.plugins:maven-dependency-plugin:pom:3.7.0 (absent): Could not transfer artifact org.apache.maven.plugins:maven-dependency-plugin:pom:3.7.0 from/to central (https://repo.maven.apache.org/maven2): sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target Downloading from central: https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-release-plugin/3.0.1/maven-release-plugin-3.0.1.pom [WARNING] Failed to retrieve plugin descriptor for org.apache.maven.plugins:maven-release-plugin:3.0.1: Plugin org.apache.maven.plugins:maven-release-plugin:3.0.1 or one of its dependencies could not be resolved: The following artifacts could not be resolved: org.apache.maven.plugins:maven-release-plugin:pom:3.0.1 (absent): Could not transfer artifact org.apache.maven.plugins:maven-release-plugin:pom:3.0.1 from/to central (https://repo.maven.apache.org/maven2): sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target Downloading from central: https://repo.maven.apache.org/maven2/org/codehaus/mojo/maven-metadata.xml Downloading from central: https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-metadata.xml [WARNING] Could not transfer metadata org.apache.maven.plugins/maven-metadata.xml from/to central (https://repo.maven.apache.org/maven2): sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target [WARNING] Could not transfer metadata org.codehaus.mojo/maven-metadata.xml from/to central (https://repo.maven.apache.org/maven2): sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target [WARNING] org.apache.maven.plugins/maven-metadata.xml failed to transfer from https://repo.maven.apache.org/maven2 during a previous attempt. This failure was cached in the local repository and resolution will not be reattempted until the update interval of central has elapsed or updates are forced. Original error: Could not transfer metadata org.apache.maven.plugins/maven-metadata.xml from/to central (https://repo.maven.apache.org/maven2): sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target [WARNING] org.codehaus.mojo/maven-metadata.xml failed to transfer from https://repo.maven.apache.org/maven2 during a previous attempt. This failure was cached in the local repository and resolution will not be reattempted until the update interval of central has elapsed or updates are forced. Original error: Could not transfer metadata org.codehaus.mojo/maven-metadata.xml from/to central (https://repo.maven.apache.org/maven2): sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target [INFO] ------------------------------------------------------------------------ [INFO] BUILD FAILURE [INFO] ------------------------------------------------------------------------ [INFO] Total time: 4.948 s [INFO] Finished at: 2025-10-23T12:28:49+08:00 [INFO] ------------------------------------------------------------------------ [ERROR] No plugin found for prefix 'help' in the current project and in the plugin groups [org.apache.maven.plugins, org.codehaus.mojo] available from the repositories [local (D:\JavaMaven\apache-maven-3.9.11\repo), central (https://repo.maven.apache.org/maven2)] -> [Help 1] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/NoPluginFoundForPrefixException
10-24
<url>https://repo.maven.apache.org/maven2</url> <id>central <url>https://repo.maven.apache.org/maven2</url> ``` 若处于内网环境，需要配置私有仓库地址。另外，检查插件版本是否与Maven版本兼容...
在构建期间出错。 在项目“acmr-ybms”中运行构建器“Maven Project Builder”时出错。 Could not calculate build plan: Plugin org.apache.maven.plugins:maven-war-plugin:2.2 or one of its dependencies could not be resolved: Failed to read artifact descriptor for org.apache.maven.plugins:maven-war-plugin:jar:2.2 Plugin org.apache.maven.plugins:maven-war-plugin:2.2 or one of its dependencies could not be resolved: Failed to read artifact descriptor for org.apache.maven.plugins:maven-war-plugin:jar:2.2 Could not calculate build plan: Plugin org.apache.maven.plugins:maven-war-plugin:2.2 or one of its dependencies could not be resolved: Failed to read artifact descriptor for org.apache.maven.plugins:maven-war-plugin:jar:2.2 Plugin org.apache.maven.plugins:maven-war-plugin:2.2 or one of its dependencies could not be resolved: Failed to read artifact descriptor for org.apache.maven.plugins:maven-war-plugin:jar:2.2 怎么解决
最新发布
11-22
### 解决项目"acmr-ybms"中Maven Project Builder构建时org.apache.maven.plugins:maven-war-plugin:2.2及其依赖无法解析的问题 您在项目"acmr-ybms"运行Maven Project Builder时，遇到插件`org.apache.maven....
使用原型骨架创建Maven项目时遇到Could not transfer metadata org.apache.maven.plugins的解决方案
y976985531的博客
08-21 4393
在使用骨架创建maven项目时，提示无法下载的问题Could not transfer metadata org.apache.maven.plugins:maven-archetype-plugin/maven-metadata.xml from/to aliyunmaven (https://maven.aliyun.com/repository/public): Transfer failed for https://maven.aliyun.com/repository/public/org/apa
Maven创建原型骨架出现Could not transfer metadata org.apache.maven.plugins:
shumaoa的博客
04-20 564
Maven原型骨架创建报错
Could not transfer metadata org.apache.maven.plugins:maven-archetype-plugin/maven-metadata.xml from
weixin_44893467的博客
12-04 708
在新建maven工程的时候，出现了一个之前没遇到的问题，具体问题截图如下： 然后找了一大堆帖子。 然后有让改镜像的，然后有让改settings.xml的，还有说网速的，找了好几篇帖子才找到正确的 如果大家也遇到这种问题，接下来就给大家解决： 这个是证书出现问题，只要在idea的这个位置加上： -Dmaven.wagon.http.ssl.insecure=true -Dmaven.wagon.http.ssl.allowall=true -Dmaven.wagon.http.ssl.ignore.val
Could not transfer metadata org.apache.maven.plugins/maven-metadata.xml from
qq_27545003的博客
04-11 3123
原因：从阿里云镜像仓库下载不了依赖文件。 解决办法：1、在IDEA里面 File --> Settings --> Build, Execution, Deployment --> Build Tools --> Maven --> Runner 的VM Options 设置： -Dmaven.wagon.http.ssl.insecure=true -Dmaven.wagon.http.ssl.allowall=true -Dmaven.wagon.http.ss...
如何解决Could not transfer metadata org.apache.maven.plugins:maven-archetype-plugin/..
xgysimida的博客
09-10 1万+
使用idea新建Maven项目的时候报了Could not transfer metadata org.apache.maven.plugins:maven-archetype-plugin/maven-metadata.xml from/to alimaven (http://maven.aliyun.com/nexus/content/repositories/central/): Transfer failed for http://maven.aliyun.com/nexus/content/rep
【Maven】入门开发过程中遇到的问题：Could not transfer metadata
热门推荐
playadota的博客
10-13 6万+
最近加入新公司，从公司gitlib上下载了一个工程进行入手。 该项目用到了很多公司自己的依赖，由于我刚来所以很多依赖需要配置maven的setting.xml和工程pom文件下载，在这里为了省事直接拷贝了部门老大的setting文件以及pom。 然后maven build--clean install，进行编译 在编译项目的过程中发现很多公司私有依赖无法下载，原因是无法连接到服务器，请求被拒
Could not transfer metadata maven-metadata.xml 
kasnfia的博客
03-04 1万+
Failure to transfer com.iii:iii-adex:1.0-SNAPSHOT/maven-metadata.xml">com.iii:iii-adex:1.0-SNAPSHOT/maven-metadata.xml from http://XXX.XXX.XX.com/artifactory/life">http://XXX.XXX.XX.com/artifactory/life was cached in the local repository, resolutio..
解决在IDEA中使用Maven遇到[WARNING] Could not transfer metadata org.apache.maven.plugins:的问题【maven在idea中的配置】
qq_37377240的博客
07-03 3894
参考链接：https://blog.csdn.net/shaozi08/article/details/105147438/ 配置文件中的mirror <mirror> <id>aliyunmaven</id> <mirrorOf>*</mirrorOf> <name>aliyun maven</name> <url>https://maven.aliyun.
评论
成就一亿技术人!
拼手气红包6.0元
还能输入1000个字符
 
红包 添加红包
表情包 插入表情
表情包 代码片
 条评论被折叠 查看
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值