[
https://issues.apache.org/jira/browse/SCM-612?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17962247#comment-17962247
]
ASF GitHub Bot commented on SCM-612:
------------------------------------
jira-importer commented on issue #822:
URL: https://github.com/apache/maven-scm/issues/822#issuecomment-2964625942
**[Rigaud
Olivier](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=olivierr)**
commented
Hi,
any news on this?
I experienced the same issue.
I have a multi module project. Until now I had a job Jenkins with the
command release:prepare and perform. But the version was changed on every
module. Now I would like to be able to change the version of a specific module
independantly of the others.
So in the pom parent I deleted the module.
In the child, I let the reference to the parent.
When I run my command on the parent, everything is fine. Every module except
one are released and deployed on nexus. Perfect.
Then, I run the commande on the specific module, and I have the error with
the code 255 while pushing...
I tried to put the URL of the SCM in the child without any effet....
I tried to force the version of :
maven-release-plugin : 2.4.1
maven-scm-provider-hg : 1.8.1
without any effect too...
> maven-release-plugin causes mercurial scm provider to fail when only a module
> is released
> -----------------------------------------------------------------------------------------
>
> Key: SCM-612
> URL: https://issues.apache.org/jira/browse/SCM-612
> Project: Maven SCM (Moved to GitHub Issues)
> Issue Type: Bug
> Components: maven-scm-provider-mercurial (hg)
> Affects Versions: 1.4, 1.5
> Reporter: Andreas Ebbert-Karroum
> Assignee: Olivier Lamy
> Priority: Major
> Attachments: hg-repo.zip
>
>
> 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 was sent by Atlassian Jira
(v8.20.10#820010)
