Hello,
I erroneously opened the issue in the SCM plugin
(https://jira.codehaus.org/browse/SCM-655), however it is an issue of
MRELEASE probably. Would someone with the according rights move it to
http://jira.codehaus.org/browse/MRELEASE, please?
Best regards Mirko
On Mon, Dec 19, 2011 at 22:56,
https://jira.codehaus.org/browse/MRELEASE-723
From: mfriedenha...@gmail.com
Date: Tue, 20 Dec 2011 21:14:59 +0100
Subject: Re: maven-release-plugin: using git where do I see the tag used to
build the release in the pom?
To: dev@maven.apache.org
Hello,
I erroneously opened the
As discussed on the user-list:
On Fri, Dec 16, 2011 at 22:58, Mirko Friedenhagen
mfriedenha...@gmail.com wrote:
Hello,
I know that with SVN the developerConnection and connection are
updated to the real URL, that is when I invoke release:prepare
with
a URL
On 19 December 2011 10:45, Mirko Friedenhagen mfriedenha...@gmail.com wrote:
As discussed on the user-list:
On Fri, Dec 16, 2011 at 22:58, Mirko Friedenhagen
mfriedenha...@gmail.com wrote:
Hello,
I know that with SVN the developerConnection and connection are
updated
some scm providers have something implemented.
for git it's : git rev-parse --verify HEAD
for svn: svn info
for hg: hg id
more details on those providers in various Info command impls.
2011/12/19 Stephen Connolly stephen.alan.conno...@gmail.com:
On 19 December 2011 10:45, Mirko Friedenhagen
Hm, this will be a hard one. I know detected, that the rewrite of the
SCM section happens in the maven-release-plugin
(org.apache.maven.shared.release.phase.RewritePomsForReleasePhase).
Two problemes I encountered now:
- The maven-scm-plugin does not seem to implement the equivalent of
scm:info
Then it will have to be the tag name so...
On 19 December 2011 21:28, Mirko Friedenhagen mfriedenha...@gmail.com wrote:
Hm, this will be a hard one. I know detected, that the rewrite of the
SCM section happens in the maven-release-plugin
