You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Anish Thomas Alex (JIRA)" <ji...@apache.org> on 2016/02/19 15:19:18 UTC
[jira] [Commented] (MRELEASE-900) release:prepare goal uses parent
directory of real repository location
[ https://issues.apache.org/jira/browse/MRELEASE-900?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15154259#comment-15154259 ]
Anish Thomas Alex commented on MRELEASE-900:
--------------------------------------------
Any updates on this issue, I am facing the same issue.
Without fix for this using maven / git is a no-go for us.
> release:prepare goal uses parent directory of real repository location
> ----------------------------------------------------------------------
>
> Key: MRELEASE-900
> URL: https://issues.apache.org/jira/browse/MRELEASE-900
> Project: Maven Release Plugin
> Issue Type: Bug
> Components: prepare
> 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://git@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://git@my-git-server.example.com:10022/somebody/ instead of ssh://git@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://git@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.3.4#6332)