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... -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
