You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Ringo De Smet (JIRA)" <ji...@codehaus.org> on 2011/02/17 11:42:22 UTC
[jira] Commented: (SCM-610) Use 'hg log --date' for changelog
generation on a date range
[ http://jira.codehaus.org/browse/SCM-610?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=256509#action_256509 ]
Ringo De Smet commented on SCM-610:
-----------------------------------
I started working on this one. Progress can be monitored here:
https://github.com/ringods/maven-scm/tree/SCM-610
> Use 'hg log --date' for changelog generation on a date range
> ------------------------------------------------------------
>
> Key: SCM-610
> URL: http://jira.codehaus.org/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 is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira