[
https://issues.apache.org/jira/browse/SCM-948?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17240254#comment-17240254
]
Clemens Quoß commented on SCM-948:
----------------------------------
Bug is a better type for this. Thought maybe because it was not exposed in the
mojo before. But yeah, internally it should have already been usable. Changed.
Would need some guidance on how to tackle this issue. Easiest way would be to
expose more executeChangeLogCommand(...) methods with distinct parms on
AbstractChangeCommandLevel. But that is deprecated.
One should use the request and hand him down, from what i understand. But that
might result in a lot of things to change across all providers. Please advice.
> Make gitexe provider use the limit parameter in changelog request.
> ------------------------------------------------------------------
>
> Key: SCM-948
> URL: https://issues.apache.org/jira/browse/SCM-948
> Project: Maven SCM
> Issue Type: Bug
> Components: maven-scm-provider-gitexe
> Affects Versions: 1.11.2
> Reporter: Clemens Quoß
> Priority: Major
>
> The gitexe ignores the limit parameter of the changelog request. It is not
> handed over in implementation of executeCommand(...) in class
> AbstractChangeLogCommand.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
