[
https://issues.apache.org/jira/browse/MRELEASE-916?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov closed MRELEASE-916.
-----------------------------------
Resolution: Incomplete
No information provided for years.
> release:prepare attempts to push to different git repo
> ------------------------------------------------------
>
> Key: MRELEASE-916
> URL: https://issues.apache.org/jira/browse/MRELEASE-916
> Project: Maven Release Plugin
> Issue Type: Bug
> Components: prepare
> Affects Versions: 2.5.2
> Reporter: Steve Suehs
> Priority: Major
>
> The documentation describing the scm format is at:
> https://maven.apache.org/scm/git.html
> and it suggests the format
> {code}
> scm:git:ssh://github.com/path_to_repository
> {code}
> Ours is similar to (redacted)
> {code}
> <scm>
> <url>https://github.com/mycompany/my_api/</url>
>
> <developerConnection>scm:git:ssh://[email protected]:mycompany/my_api.git</developerConnection>
>
> <connection>scm:git:ssh://[email protected]:mycompany/my_api.git</connection>
> </scm>
> {code}
> When the maven-release-plugin attempts to push, it specifies
> {code}
> Executing: /bin/sh -c cd /home/ssuehs/work/my_api && git push
> ssh://[email protected]:mycompany/my_api.git
> refs/heads/mvnreleasework:refs/heads/mvnreleasework
> {code}
> Note the {{ssh}}. In deed, executing this from an interactive command prompt
> also does not work.
> Which is correct? The documentation? The plugin? Or could be I am just wrong.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
