I had a look :-D . The class code boils down to executing 'git tag -F
messageFile' AFAICS. So there is no sign in a released POM how the tagname
was. Would it be an useful enhancement to put either the hash or the
tagname into the POM?
Regards Mirko
--
Sent from my phone
yes
- Stephen
---
Sent from my Android phone, so random spelling mistakes, random nonsense
words and other nonsense are a direct result of using swype to type on the
screen
On 18 Dec 2011 17:41, Mirko Friedenhagen mfriedenha...@gmail.com wrote:
I had a look :-D . The class code boils down to
OK, I will open an issue in the SCM plugin and give it a try :-D .
Regards Mirko
--
Sent from my phone
http://illegalstateexception.blogspot.com
http://github.com/mfriedenhagen/
https://bitbucket.org/mfriedenhagen/
On Dec 18, 2011 11:14 PM, Stephen Connolly
stephen.alan.conno...@gmail.com
No comments on this? How would a scm:bootstrap know which tag to build with git?
Regards Mirko
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
Hi Mirko,
Did you have a look at the related code?
http://maven.apache.org/scm/maven-scm-providers/maven-scm-providers-git/maven-scm-provider-gitexe/xref/org/apache/maven/scm/provider/git/gitexe/command/tag/GitTagCommand.html
-Robert
From: mfriedenha...@gmail.com
Date: Sat, 17 Dec
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 like:
https://SVNSERVER/svn/REPO/myproject/branches/release it will be
replaced by https://SVNSERVER/svn/REPO/myproject/tags/myproject-1.0
which is fine
