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 Fri, 18 May 2018 20:16:00 GMT


ASF GitHub Bot commented on SCM-885:

michael-o commented on issue #74: [SCM-885] third implementation
   Why did you rename the test repo and have added a new one? What was actually wrong with
the given one? The are a lot of sample hooks which aren't superfluous for the test (they may
have existed in the previous repo also).

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
>            Assignee: Michael Osipov
>            Priority: Major
>             Fix For: 1.9.6
>         Attachments: scm-885-different-behavior-exe-jgit-patch.diff
> 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