[
https://issues.apache.org/jira/browse/SCM-885?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16477997#comment-16477997
]
Michael Osipov commented on SCM-885:
------------------------------------
[~McFoggy], looking into your patch. The documentation says:
bq. Returns the changes that have happend in the source control system in a
certain period of time. This can be adding, removing, updating, ... of files
This does not concretely specify how it has to be implemented. It is at the
descretion of the SCM. Look at svnexe, it does use {{:HEAD}}. We could probably
add {{HEAD}} for the sake of completeness.
Regarding JGit, neither this is wrong or right because it is not specified. I
think we need to do what makes most sense for Git.
> GitChangeLogCommand is wrong when only endVersion is set
> --------------------------------------------------------
>
> Key: SCM-885
> URL: https://issues.apache.org/jira/browse/SCM-885
> 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
(v7.6.3#76005)
