You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Michael Osipov (JIRA)" <ji...@apache.org> on 2015/09/06 22:45:51 UTC
[jira] [Closed] (SCM-610) Use 'hg log --date' for changelog
generation on a date range
[ https://issues.apache.org/jira/browse/SCM-610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael Osipov closed SCM-610.
------------------------------
Resolution: Auto Closed
This issue has been auto closed because it has been inactive for a long period of time. If you think this issue still applies, retest your problem with the most recent version of Maven and the affected component, reopen and post your results.
> Use 'hg log --date' for changelog generation on a date range
> ------------------------------------------------------------
>
> Key: SCM-610
> URL: https://issues.apache.org/jira/browse/SCM-610
> Project: Maven SCM
> Issue Type: Improvement
> Components: maven-scm-provider-mercurial (hg)
> Affects Versions: 1.4
> Reporter: Ringo De Smet
>
> The current implementation of the ChangeLogCommand for hg repositories first gets the commit info for the complete repository, only filtering on the dates afterwards in the Java level. The 'hg' binary has the option --date since version 0.9.2, which is the version listed as the minimum version this provider is compatible with.
> Running "hg help dates" gives you an overview of the options one has to specify a date range on the command line. The provider should be updated to use the 'hg' feature instead of filtering itself.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)