[ 
https://issues.apache.org/jira/browse/SCM-659?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17962462#comment-17962462
 ] 

ASF GitHub Bot commented on SCM-659:
------------------------------------

jira-importer opened a new issue, #870:
URL: https://github.com/apache/maven-scm/issues/870

   **[Paul 
Hicks](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=tenwit)** 
opened 
**[SCM-659](https://issues.apache.org/jira/browse/SCM-659?redirect=false)** and 
commented
   
   I need to use the output of "git describe" with the buildnumber plugin. The 
newest versions of gitexe scm are using "git rev-parse --verify HEAD" which is 
a sensible choice, but won't work for me. Is there a way to configure how the 
info method works? I can't find a definition of the API.
   
   I'd be happy to develop this and submit a patch. I just need to know how 
individual methods in the SCM plugin are configured. I'm not having any luck 
with http://maven.apache.org/scm/maven-scm-api/
   
   
   ---
   
   **Affects:** 1.6
   




> gitexe SCM: Configurability of SCM info method 
> -----------------------------------------------
>
>                 Key: SCM-659
>                 URL: https://issues.apache.org/jira/browse/SCM-659
>             Project: Maven SCM (Moved to GitHub Issues)
>          Issue Type: Improvement
>          Components: maven-scm-provider-gitexe
>    Affects Versions: 1.6
>            Reporter: Paul Hicks
>            Priority: Minor
>
> I need to use the output of "git describe" with the buildnumber plugin. The 
> newest versions of gitexe scm are using "git rev-parse --verify HEAD" which 
> is a sensible choice, but won't work for me. Is there a way to configure how 
> the info method works? I can't find a definition of the API.
> I'd be happy to develop this and submit a patch. I just need to know how 
> individual methods in the SCM plugin are configured. I'm not having any luck 
> with http://maven.apache.org/scm/maven-scm-api/



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to