【解决Maven 报 Return code is: 400 , ReasonPhrase:Repository version policy: SNAPSHOT does not allow version: 2.1.0.RELEASE. 的错误】的更多相关文章

解决Maven 报 Return code is: 400 , ReasonPhrase:Repository version policy: SNAPSHOT does not allow version: 2.1.0.RELEASE. 的错误

最近在搭建公司的基础框架,业务需求用到elasticsearch,所以需要整合到基础框架里,供各业务线使用同时也便于管理,但在整合的过程中,出现了莫名的问题,同时maven的提示也不够明确. 我的版本信息为 spring boot 2.1.0.RELEASE,elasticsearch 6.3.1,因为不同版本可能遇到的问题不一样.       我的POM包引用为 <parent> <groupId>org.springframework.boot</groupId>…

Maven私有仓库: 发布release版本报错：Return code is: 400, ReasonPhrase: Repository does not allow upd ating assets: maven-releases.

今天在将一个maven组件由SNAPSHORT升级为正式版本1.0.0,然后执行发布: mvn clean deploy -pl ielong-common -am -DskipTests, 报错:Return code is: 400, ReasonPhrase: Repository does not allow upd ating assets: maven-releases. 经排查发现是因为重复发布导致的.maven私有仓库默认不允许重复部署. 进入maven-releases的配置界…

maven deploy Return code is: 400, ReasonPhrase: Bad Request.

最近在自己本地deploy jar 到本地 nexus的时候,报错 Return code is: 400, ReasonPhrase: Bad Request. 解决思路: 1.查看maven profile .查看下图的配置和maven配置文件settings.xml中的server.repositories 配置是否一致. 这里主要是看相应的id,对应的用户名.密码.url之类的配置是否正确. 2.如下图:设置对应仓库的 Deployment Policy…

mvn deploy 报错：Return code is: 400, ReasonPhrase: Bad Request. ->

mvn deploy 报错:Return code is: 400, ReasonPhrase: Bad Request. -> TEST通过没有报错,但是最终部署到Nexus中时出现错误. 后检查发现,pom中的上传releases 和 snapshots的配置颠倒了. 要跟nexus上的配置一对一对应 来自为知笔记(Wiz)…

Maven deploy Return code is: 400

Maven deploy Return code is: 400 学习了:https://blog.csdn.net/running_snail_/article/details/19821777 Hosted格式的才可以部署: group形式的把其它几个库都进行了组合:mirro配置一个group仓库就可以全部访问了: 如果需要进行deploy,需要是hosted格式的仓库: 在settings.xml中需要配置: <activeProfiles><activeProfile>x…

Maven-008-Nexus 私服部署发布报错 Failed to deploy artifacts: Failed to transfer file: ... Return code is: 4XX, ReasonPhrase: ... 解决方案

我在部署构件至 maven nexus 私服时,有时会出现 Failed to deploy artifacts: Failed to transfer file: ... Return code is: 4XX, ReasonPhrase: ... 类似这样的错误,那么这些错误是怎么产生,又如何解决呢?我在此将自己在部署过程中遇到的错误整理汇总一下,供大家参阅,希望对大家有所帮助. 一.错误的请求.Return code is: 400, ReasonPhrase: Bad Request.…

maven报错：Return code is: 501 , ReasonPhrase:HTTPS Required

今天把一个去年没做完的项目翻出来做时,发现maven无法正常导入依赖.检查了一遍项目配置,没发现有什么问题.而且依赖在本地仓库存在. 随后发现报错:Failed to transfer file:*********. Return code is: 501 , ReasonPhrase:HTTPS Required. 这时候好像发现了什么重点————我们需要将maven配置修改一下: <!-- 中央仓库1 --> <mirror> <id>repo1</id>…

【Maven错误】 Non-resolvable parent POM for ...... Return code is: 500 , ReasonPhrase:Internal Server Error. and 'parent.relativePath' points at no local POM @ line 14, column 11

一.异常信息 [INFO] Scanning for projects... Downloading: http://www.myhost.com/maven/jdk18/org/springframework/boot/spring-boot-starter-parent/2.1.1.RELEASE/spring-boot-starter-parent-2.1.1.RELEASE.pom Downloading: http://nexus.jiushiyaokuaile.cn/nexus/co…

QA:Failed to deploy artifacts from/to snapshots XX Failed to transfer file Return code is: 405, ReasonPhrase:Method Not Allowed.

QA: Failed to deploy artifacts from/to snapshots XX Failed to transfer file Return code is: 405, ReasonPhrase:Method Not Allowed. Solution: maven目录conf的setting.xml里, <server> <id>releases</id> <username>admin</username> <p…

[转]解决Maven报错"Plugin execution not covered by lifecycle configuration"

[转]解决Maven报错"Plugin execution not covered by lifecycle configuration" 导入Myabtis源码后,POM文件会报出如下异常: Plugin execution not covered by lifecycle configuration org.sonatype.plugins:jarjar-maven-plugin Plugin execution not covered by lifecycle configura…