maven-release-plugin causes mercurial scm provider to fail when only a module
is released
-----------------------------------------------------------------------------------------
Key: SCM-612
URL: http://jira.codehaus.org/browse/SCM-612
Project: Maven SCM
Issue Type: Bug
Components: maven-scm-provider-mercurial (hg)
Affects Versions: 1.4, 1.5
Reporter: Andreas Ebbert-Karroum
Problem as described on the [maven-users mailing
list|http://maven.40175.n5.nabble.com/How-to-release-a-single-module-in-a-Mercurial-repository-tp3406421p3406421.html].
Basically it is not possible to release a single module from a multi-module
project with mercurial as scm provider.
h2. When trying with current 1.5-SNAPSHOT:
{code}
Caused by: org.apache.maven.scm.ScmException: This provider doesn't support
tagging subsets of a directory
at
org.apache.maven.scm.provider.hg.command.tag.HgTagCommand.executeTagCommand(HgTagCommand.java:77)
at
org.apache.maven.scm.command.tag.AbstractTagCommand.executeCommand(AbstractTagCommand.java:81)
at
org.apache.maven.scm.command.AbstractCommand.execute(AbstractCommand.java:59)
... 29 more
{code}
h2. When trying with 1.4 release
It is more complicated, but also does not work. It boils down to having a
mandatory pom.xml in the repository root and scm url messed up during the
release:prepare and release:perform phases. See mentioned email for more
details.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
