Maven uploadArchives命令报错：Could not deploy to remote repository | Failed to deploy artifacts/metadata

最新推荐文章于 2022-07-28 10:29:00 发布
原创 最新推荐文章于 2022-07-28 10:29:00 发布 · 3.9k 阅读 · 0 ·
CC 4.0 BY-SA版权
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。

本文介绍如何使用AndroidStudio与Gradle将AAR文件上传至Maven仓库，包括配置repository、pom信息及常见错误排查。重点解决上传过程中因变量格式问题导致的连接失败。

Android Studio使用gradle上传aar到maven仓库

uploadArchives {
   
   
    repositories {
   
   
        mavenDeployer {
   
   
            repository(url: NEXUS_REPOSITORY_URL) {
   
   
                authentication(userName: getRepositoryUserName(), password: getRepositoryPassword
最低0.47元/天 解锁文章
【maven】mvn deploy 报错 Failed to deploy artifacts: Could not transfer artifact
九师兄
06-03 8627
1.场景1 1.1 概述 因为在windows下，内网环境，然后升级了flink，但是包是外网拷贝进去的，拷贝到我的本地，现在本地升级好了，需要将jar包发布到内网的nexus机器中，但是执行命令报错如下 问题报错： [ERROR] Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.8.2:deploy (default-deploy) on project apollo: Failed to deploy arti.
Android组件化开发（一）--Maven私服的搭建
yuhaibing111的博客
11-02 1654
组件化开发中的Maven私服搭建
deploy上传nexus私服报错:Failed to deploy artifacts:Failed to transfer file *** with status code 400
sun_luming的博客
01-20 8468
这种问题报错大同小异，有以下几个关键提示： Failed to deploy artifacts 部署文件失败 Failed to transfer file 文件传输失败 with status code 400 400部署异常 如下图： 这里有必要先说说jar包上传nexus私服成功的几个条件： ①检查私服运行状态 查看私服状态命令： nexus.exe /status 结果显示：nexus私服运行中 ②项目pom.xml文件中distributionMana
Maven-008-Nexus 私服部署发布报错 Failed to deploy artifacts: Failed to transfer file: ... Return code is: 4X
Angus的博客
06-25 1万+
我在部署构件至 maven nexus 私服时，有时会出现 Failed to deploy artifacts: Failed to transfer file: … Return code is: 4XX, ReasonPhrase: … 类似这样的错误，那么这些错误是怎么产生，又如何解决呢？我在此将自己在部署过程中遇到的错误整理汇总一下，供大家参阅，希望对大家有所帮助。 一、错误的请求。Re...
Maven报错：Failed to deploy artifacts: Could not transfer artifact from/to snapshots 401 Unauthorize
Cyms,BgXmSfXtsj !!!! Battle Each Moment !!!!
07-28 4181
Maven deploy报错： Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:deploy (default-deploy) on project : Failed to deploy artifacts: Could not transfer artifact from/to snapshots 4...
Failed to deploy artifacts: Could not transfer artifact ReasonPhrase: Bad credentials
jianchihubo的博客
12-31 9478
加入项目以后没有deploy的能力,开始以为自己是新人,没有分给自己权限,也没再问. 后来不部署代码很不方便就跟项目经理去要,结果人家说根本没设置什么权限. 后来跟同事要了他的maven配置文件,发现里面也没什么特别的设置. 最后发现自己的maven版本是3.6.0同事用的3.3.9,版本降下来以后就好了. 这只是本人遇到的问题,并不代表这个报错就是这么解决,有类似情况的同学可以这么尝试...
[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
另外，检查插件版本是否与Maven版本兼容，尝试更新插件版本。 ### 解决PKIX路径构建失败问题 PKIX路径构建失败通常是由于证书验证问题。可以修改JDK配置文件，处理证书路径时禁用的算法和处理SSL/TLS时禁用的算法全...
【IDEA】 导入maven项目报错 Could not transfer artifact com.XX.XX:XX(PKIX path building failed)
程序媛一枚
03-10 4485
导入maven项目报错 Could not transfer artifact com.XX.XX:XX(PKIX path building failed)
deploy报错Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:3.1.1:deploy (default-deploy) on project solution-components-cache-ohc: Failed to deploy artifacts/metadata: Cannot access ${smb.repository.url} with type default using the available connector factories: BasicRepositoryConnectorFactory: Cannot access ${smb.repository.url} using the registered transporter factories: HttpTransporterFactory, FileTransporterFactory, WagonTransporterFactory -> [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/MojoExecutionException
10-22
</think>针对Maven部署时出现的`Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:3.1.1:deploy (default-deploy)`错误，核心问题是Maven无法访问仓库URL `${smb.repository.url}`。...
Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:3.1.1:deploy-file (default-cli) on project convert-plugin-excel: Failed to deploy artifacts: Could not transfer artifact com.huawei.apaasinnovation:convert-plugin-excel:jar:1.24.0-2025062404-RELEASE from/to fuxi-release (https://maven.cloudartifact.lfg.dragon.tools.huawei.com/artifactory/Product-Public-Service): transfer failed for https://maven.cloudartifact.lfg.dragon.tools.huawei.com/artifactory/Product-Public-Service/com/huawei/apaasinnovation/convert-plugin-excel/1.24.0-2025062404-RELEASE/convert-plugin-excel-1.24.0-2025062404-RELEASE.jar, status: 409 -> [Help 1]
06-26
在部署JAR包到私有仓库时，Maven的`maven-deploy-plugin`报告“409 Conflict”错误通常表示目标仓库中已经存在相同版本的构件（artifact），或者由于仓库配置或权限问题导致无法成功部署。以下是对该问题的详细分析...
gradle-maven-publish-plugin,gradle插件，配置一个uploadarchives任务，自动将所有java、kotlin或android库上载到任何maven实例。.zip
10-11
Gradle插件，创建一个UploadArchives任务，自动将所有Java、Kotlin或Android库上载到任何Maven实例。这个插件基于chris-banes的初始实现，并且已经被增强以添加kotlin支持并跟上最新的更改。
mvn -deploy 报错 Failed to deploy artifacts: Could not transfer artifact
热门推荐
forliberty的博客
10-24 4万+
问题报错：[ERROR] Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.8.2:deploy (default-deploy) on project apollo: Failed to deploy artifacts: Could not transfer artifact com.ctrip.frame
Failed to deploy artifacts: Could not tran sfer artifact （省略）400 Repository version policy: SNAPSHOT
weixin_40583191的博客
03-29 3243
向本地私服发布jar包的时候报错： Failed to deploy artifacts: Could not transfer artifact com.***😗**:jar:1.0.3-SNAPSHOTS from/to aws (http://***:port/repository/maven-snapshots/): Transfer failed for http://***:port/repository/maven-snapshots/com/***/***/1.0.3-SNAPSHOTS/*
发布Jar到中央仓库报错 Remote staging failed: Staging rules failure!
nkxrb
12-04 1636
发布Jar到中央仓库报错 Remote staging failed: Staging rules failure! 意思是： 未遵守发布jar的规则，可以查看命令行中详细的错误描述【error】… 如果是手动发布，即在https://oss.sonatype.org/网址上发布的，可以点开页面下方的日志列表，查看错误描述。 可能原因有： 是否已经发布公钥： ps:使用 gpg4win（一个软件...
Nexus 私服部署发布报错 Failed to deploy artifacts: Failed to transfer file: ... Return code is: 4X
iechenyb专栏
10-17 1973
我在部署构件至 maven nexus 私服时，有时会出现 Failed to deploy artifacts: Failed to transfer file: ... Return code is: 4XX, ReasonPhrase: ... 类似这样的错误，那么这些错误是怎么产生，又如何解决呢？我在此将自己在部署过程中遇到的错误整理汇总一下，供大家参阅，希望对大家有所帮助。 　　...
填坑：有工程依赖时，Gradle uploadArchives to Nexus/Maven
chuyouyinghe的专栏
01-11 787
很多时候，Android Studio中所创建的工程，会依赖一个或多个Module。Module 生成的AAR库，可以上传到maven或者私服Nexus作为公用的SDK。Gradle子工程之间通过 compile/implementation project(":XXX")这种方式依赖是非常便利的，但是这样的时候，如果用uploadArchives上传AAR到Maven，生成的pom.xml是不正确的,以致于在工程中依赖我们上传的库时，无法找到它如下图所示： 所以本文记录在这种情况下，如何上传AAR到
maven3 deploy执行报错
fishyych
09-22 309
在maven2下面编译运行非常正常的项目，到了maven3下面做release:deploy的时候报如下错误： [INFO] [INFO] ------------------------------------------------------------------------ [INFO] [ERROR] Failed to execute goal org.apache.mave...
将自己的jar上传到mavn仓库中遇到的问题
wuqingsssss的博客
04-22 1065
deploy to sonatype 参考1：https://www.cnblogs.com/windliu/p/9524478.html 参考2：https://www.cnblogs.com/songyz/p/11387978.html 1申请sonatype账号 申请账号的地址在这里: https://issues.sonatype.org/secure/Signup!default.jspa 申请完成之后，我们需要提供相应的项目信息，地址在这里:https://issues.sonatype.org
Android上的依赖库简介
城主的专栏
09-27 3583
android不但可以引用jar包，而且还有自己的特殊jar包–aar压缩包。一、aar的生成方法1、直接make project生成aar在生成AAR的时候，先创建一个Library的Module，然后Build –> Make project（或者gradle clean build）就可以在build/outputs/aar下生成xxx.aar文件。 以上方法会有个问题：依赖的第三方比如de
评论
成就一亿技术人!
拼手气红包6.0元
还能输入1000个字符
 
红包 添加红包
表情包 插入表情
表情包 代码片
 条评论被折叠 查看
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

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

抵扣说明：

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

余额充值