maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Osipov (JIRA)" <>
Subject [jira] [Commented] (SCM-885) GitChangeLogCommand is wrong when only endVersion is set
Date Wed, 16 May 2018 20:31:00 GMT


Michael Osipov commented on SCM-885:

The more I think about it, the more I have the feeling that won't be able to cover all cases
for Git anyway. We can reduce gitexe and jgit down to these three case where a new parameter
is not necessary:


{{START}}, {{END}} those are explicitly provided. The rest is omitted. WDYT?

> 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
>             Fix For: waiting-for-feedback
>         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