maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (SCM-885) GitChangeLogCommand is wrong when only endVersion is set
Date Thu, 03 May 2018 11:40:00 GMT


ASF GitHub Bot commented on SCM-885:

McFoggy opened a new pull request #70: [SCM-885] allow to use only endVersion in GitChangeLogCommand
   On a GitChangeLogCommand setting only endVersion allows to retrieve
   commits from project start until the commit corresponding to endVersion.
   fixes #SCM-885
   Signed-off-by: Matthieu Brouillard <>

This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:

> GitChangeLogCommand is wrong when only endVersion is set
> --------------------------------------------------------
>                 Key: SCM-885
>                 URL:
>             Project: Maven SCM
>          Issue Type: Bug
>          Components: maven-scm-provider-gitexe
>    Affects Versions: 1.9.5
>            Reporter: Matthieu Brouillard
>            Priority: Major
> Invoking execution of a GitChangeLogCommand where only the end revision has been set
produces a wrong out.
> +Actual result:+
> {{git whatchanged --date=iso  ..END_REVISION_SHA1 -- PROJECT_PATH}}
> +Expected result:+ only the end revison SHA1 is used without the two dots
> {{git whatchanged --date=iso  END_REVISION_SHA1 -- PROJECT_PATH}}

This message was sent by Atlassian JIRA

View raw message