使用Maven发布时标记子主干目录(使用SVN)
这是我的 SVN 结构:
trunk /
+- docs /
+- dev /
+- project-parent /
+- project-war /
releases /
我希望 Maven 发布插件将 /trunk/dev/
标记为 /releases/
这是我的父 pom.xml
<build>
<plugins>
<plugin>
<artifactId>maven-release-plugin</artifactId>
<version>2.1</version>
<configuration>
<tagBase>http://svn.mycompany.com/svn/project/releases</tagBase>
<generateReleasePoms>false</generateReleasePoms>
<autoVersionSubmodules>true</autoVersionSubmodules>
</configuration>
</plugin>
</plugins>
</build>
<scm>
<connection>scm:svn:http://svn.mycompany.com/svn/project/trunk/dev</connection>
<developerConnection>scm:svn:http://svn.mycompany.com/svn/project/trunk/dev</developerConnection>
</scm>
问题是,当我执行 mvn release:prepare-with-pom
时,Maven 将 /trunk
标记为 /releases/< ;发布版本>
。
有人知道如何标记 /trunk/dev
吗?谢谢 !
Here is my SVN structure :
trunk /
+- docs /
+- dev /
+- project-parent /
+- project-war /
releases /
I would like the Maven release plugin to tag /trunk/dev/
to /releases/<release-version>
Here is my parent pom.xml
<build>
<plugins>
<plugin>
<artifactId>maven-release-plugin</artifactId>
<version>2.1</version>
<configuration>
<tagBase>http://svn.mycompany.com/svn/project/releases</tagBase>
<generateReleasePoms>false</generateReleasePoms>
<autoVersionSubmodules>true</autoVersionSubmodules>
</configuration>
</plugin>
</plugins>
</build>
<scm>
<connection>scm:svn:http://svn.mycompany.com/svn/project/trunk/dev</connection>
<developerConnection>scm:svn:http://svn.mycompany.com/svn/project/trunk/dev</developerConnection>
</scm>
The problem is that when I execute mvn release:prepare-with-pom
, Maven tags /trunk
to /releases/<release-version>
.
Does someone know how to tag /trunk/dev
instead ? Thanks !
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。
![扫码二维码加入Web技术交流群](/public/img/jiaqun_03.jpg)
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(2)
这是一个解决方法:将
remoteTagging
设置为false
Here is a workaround : set
remoteTagging
tofalse
这似乎是一个错误!我在这里创建了一个问题: http://jira.codehaus.org/browse/MRELEASE-642 。
It seems to be a bug ! I've created an issue here : http://jira.codehaus.org/browse/MRELEASE-642.