[SCM-612] maven-release-plugin causes mercurial scm provider to fail when only a module is released

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Auto Closed
• Affects Version/s: 1.4, 1.5
• Component/s: maven-scm-provider-mercurial (hg)
• Assignee: Olivier Lamy
• Reporter: Andreas Ebbert-Karroum
• Created: 04/Mar/11 11:05
• Updated: 16/Mar/18 22:42
• Resolved: 16/Mar/18 22:42

Description

Problem as described on the maven-users mailing list. Basically it is not possible to release a single module from a multi-module project with mercurial as scm provider.

When trying with current 1.5-SNAPSHOT:

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 

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.