[
https://issues.apache.org/jira/browse/SCM-948?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17963768#comment-17963768
]
ASF GitHub Bot commented on SCM-948:
------------------------------------
jira-importer commented on issue #1173:
URL: https://github.com/apache/maven-scm/issues/1173#issuecomment-2964649991
**[Clemens
Quoß](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=cquoss)**
commented
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
AbstractChangeCommand level. 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 limit parameter work for svnexe and gitexe changelog goal
> --------------------------------------------------------------
>
> Key: SCM-948
> URL: https://issues.apache.org/jira/browse/SCM-948
> Project: Maven SCM (Moved to GitHub Issues)
> Issue Type: Improvement
> Components: maven-scm-provider-gitexe, maven-scm-provider-svn
> Affects Versions: 1.11.2
> Reporter: Clemens Quoß
> Assignee: Michael Osipov
> Priority: Major
> Fix For: 1.11.3
>
>
> 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.20.10#820010)
