[英]deploy on nexus artifacts with Snapshot policy but without SNAPSHOT string in version
apparently my Nexus is rejecting every deploy I throw at him if the artifact has not -SNAPSHOT in the version. 如果工件没有在版本中使用-SNAPSHOT,那么我的Nexus显然会拒绝我对他的所有部署。
Data: 数据:
I need this naming convention because I'm building one of the several experiments we run internally, as opposite to the canonical develop branch which produces a proper entando-core-engine-SNAPSHOT.jar 我需要这种命名约定,因为我正在构建我们内部运行的几个实验之一,这与产生适当的entando-core-engine-SNAPSHOT.jar的规范开发分支相反
Any advice? 有什么建议吗? I'm totally lost.
我完全迷路了。
The thing is that usually your Nexus is configured not to allow a redeployment of a release. 事实是,通常您的Nexus配置为不允许重新发布版本。 A release from Maven point of view is an artifact where it's version it NOT -SNAPSHOT .
从Maven的角度来看,发行版是一个工件,而不是它的版本-SNAPSHOT 。 In contradiction a SNAPSHOT is intended to be deployed several times into nexus.
矛盾的是,SNAPSHOT打算多次部署到联系中。
This sounds like you don't using the release plugin of Maven nor the Release PLugin of Jenkins. 听起来您好像没有使用Maven的发布插件,也没有使用Jenkins的Release PLugin。
Nexus is a repository manager that uses different repository formats, with the main format being the Maven repository format. Nexus是一个存储库管理器,它使用不同的存储库格式,主要格式为Maven存储库格式。 Changing the names of artifacts on the server is not possible since it violates the format.
无法更改服务器上工件的名称,因为它违反了格式。 They have to be located in the directory structure established by groupId, artifactId and version and use the artifactId-version-classifier.packaging for the file names.
它们必须位于由groupId,artifactId和version建立的目录结构中,并使用artifactId-version-classifier.packaging作为文件名。
If you need a different file name on the server you have to look at a different repository format (bad idea). 如果在服务器上需要其他文件名,则必须查看其他存储库格式(不好的主意)。 If you need the filename on the client just download from the correct name and rename..
如果您需要客户端上的文件名,请从正确的名称下载并重命名。
声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.