maven-issues mailing list archives

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


Matthieu Brouillard commented on SCM-885:

I have no problem with the fact that `git log` interprets `..VERSION` as `HEAD..VERSION`,
my issue is that I want, using the API, to express `FIRST_COMMIT_OF_REPO..VERSION` ie provide
a endVersion but no startVersion.

If a user wants to express `HEAD..VERSION` he has the ability to do so by explicitly providing
a startVersion of HEAD.

With my change you can then express both `FIRST_COMMIT_OF_REPO..VERSION` and `HEAD..VERSION`.

> 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
> 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