maven-release-plugin:该文件夹与 pom.xml 的 scm 部分相关吗?
我们使用标准 svn 布局(/branches/xy、/tags、/trunk)和 mvn release(即 maven-release-plugin)从分支执行发布。
我们通常会尝试确保该部分遵循分支,因此看起来像这样
<scm>
<connection>scm:svn:http://DOMAIN/svn/PROJECT/MODULE/branches/1.5</connection>
<developerConnection>( same as connection )</developerConnection>
</scm>
有人能告诉我末尾的“branches/1.5”是否是绝对必要的?或者 maven-plugin 能解决这个问题吗?如果错误会发生什么 - 假设我在 1.5 分支上,而 pom 的 scm 部分在 1.4 或主干上?我暂时没有尝试的欲望。 :-/
We're using a standard svn layout (/branches/x.y, /tags, /trunk) and mvn release (i.e. maven-release-plugin) to perform releases, from the branches.
We usually try to make sure the section follows the branch, so it looks like this
<scm>
<connection>scm:svn:http://DOMAIN/svn/PROJECT/MODULE/branches/1.5</connection>
<developerConnection>( same as connection )</developerConnection>
</scm>
Can anybody tell me whether the "branches/1.5" at the end is strictly necessary? Or does maven-plugin figure this out anyway? What happens if it's wrong - say I'm on the 1.5 branch and the scm section of the pom say 1.4, or trunk? I have no immediate desire to try it. :-/
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(1)
考虑到 Maven SCM url used fr Subversion:
,您需要的是仓库中正确的 Maven 模块。
Maven 无法自行推断该路径,因此“
branches/1.5
”是必需的。有关插图,请参阅 SO 问题“
Considering the Maven SCM url used fr Subversion:
, what you need is the path to the right Maven module within your repo.
Maven won't be able to infer that path on its own, so the '
branches/1.5
' is necessary.See for illustrations the SO question "With the maven-release-plugin, how to branch a module and its children?".