Jens Rabe created MRELEASE-900:
----------------------------------
Summary: release:prepare goal uses parent directory of real
repository location
Key: MRELEASE-900
URL: https://jira.codehaus.org/browse/MRELEASE-900
Project: Maven Release Plugin
Issue Type: Bug
Affects Versions: 2.5.1
Reporter: Jens Rabe
Priority: Blocker
I have this in my pom.xml:
{code:xml}
<scm>
<connection>scm:git:http://my-git-server.example.com/git/somebody/my-project.git</connection>
<developerConnection>ssh://g...@my-git-server.example.com:10022/somebody/my-project.git</developerConnection>
<url>http://my-git-server.example.com/git/somebody/my-project</url>
</scm>
{code}
When I do a mvn release:prepare, it tries to push the tag to
ssh://g...@my-git-server.example.com:10022/somebody/ instead of
ssh://g...@my-git-server.example.com:10022/somebody/my-project.git, causing the
release prepare to fail with "Access denied".
When I add a "fake file" at the end, like:
{code:xml}
<scm>
<connection>scm:git:http://my-git-server.example.com/git/somebody/my-project.git/.git</connection>
<developerConnection>ssh://g...@my-git-server.example.com:10022/somebody/my-project.gi/.gitt</developerConnection>
<url>http://my-git-server.example.com/git/somebody/my-project</url>
</scm>
{code}
the release:prepare works, but release:perform fails because it is using the
URL as-is.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
