[
https://jira.codehaus.org/browse/MBUILDNUM-91?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=293553#comment-293553
]
Laurent Prévost edited comment on MBUILDNUM-91 at 3/7/12 3:19 AM:
------------------------------------------------------------------
It seems that this bug is not directly related to buildnumber-maven-plugin. I
realized that the Maven-SCM-API is used and the command that is issued by the
plugin is built from this API. I open another bug to Maven-SCM-API project
http://jira.codehaus.org/browse/SCM-668.
was (Author: prevole):
It seems that this bug is not directly related to buildnumber-maven-plugin.
I realized that the Maven-SCM-API is used and the command that is issued by the
plugin is built from this API. I open another bug to Maven-SCM-API project.
> Unable to retrieve the buildNumber with SVN 1.7 and Git
> -------------------------------------------------------
>
> Key: MBUILDNUM-91
> URL: https://jira.codehaus.org/browse/MBUILDNUM-91
> Project: Mojo Build Number Maven Plugin
> Issue Type: Bug
> Affects Versions: 1.1
> Environment: Mac OS X Snow Leopard (64bits)
> Maven 2.x or 3.x
> Reporter: Laurent Prévost
>
> Since SVN 1.7 is released, I see that the buildNumber is allways impossible
> to retrieve from submodules.
> {code}
> |-Parent
> |--Child1
> |--Child2
> {code}
> When the buildnumber-maven-plugin is run on Child1 with SVN 1.7 or Git that
> have centralized repository management, the buildNumber is always null or the
> value configured through revisionOnScmFailure.
> After some trouble shooting, I discovered that this command is issued:
> {code}
> /bin/sh -c cd /tmp/temp/mytestingrepo && git rev-parse --verify --short=7 HEAD
> {code}
> But when I copy/paste this command in a shell, it fails with this error
> message
> {code}
> fatal: Not a git repository (or any of the parent directories): .git
> {code}
> So I tried this command
> {code}
> /bin/sh -c "cd /tmp/temp/mytestingrepo && git rev-parse --verify HEAD"
> {code}
> And this time it worked.
> I really do not know if the plugin do the subtle difference between these two
> syntax but anyway, in the case of SVN 1.7+ and Git 1.7.9+, it seem to be not
> possible to get the buildNumber.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email