jira-importer commented on issue #936: URL: https://github.com/apache/maven-scm/issues/936#issuecomment-2964634177
**[Daniel Soria](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=soriad)** commented When running Bamboo with several user agent in the cloud, to rely on release.properties is not an option. The problem is in maven-release-plugin. The class org.apache.maven.plugins.release.PerformReleaseMojo extends AbstractReleaseMojo, just extending AbstractScmReleaseMojo instead of AbstractReleaseMojo solves the problem (1 line of code) ``` @Mojo( name = "perform", aggregator = true, requiresProject = false ) public class PerformReleaseMojo extends AbstractScmReleaseMojo { ``` Now I can run my modified release plugin: ``` mvn org.apache.maven.plugins:maven-release-git-patched-plugin:2.4.2:perform --batch-mode -DconnectionUrl=scm:git:ssh://username@server/repo.git -Dtag=4.1.0-TB01 ``` The git clone command generated is ``` [INFO] Executing: /bin/sh -c cd /project_path/target && git clone --branch 4.1.0-TB01 ssh://username@server/repo.git /project_path/target/checkout ``` As you can see to implement the improvement is quite trivial. -- 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
