[
http://jira.codehaus.org/browse/MCHANGELOG-80?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=150560#action_150560
]
Thomas commented on MCHANGELOG-80:
----------------------------------
It would probably be better to change the patch from <revisions/> to a more
generic <versions/>, which means all the documentation will also need to be
re-changed. The Maven ScmProvider seems to work fine with SVN revision numbers
fed into it as new ScmVersion()s.
> support selecting of changes by revision-range for subversion
> -------------------------------------------------------------
>
> Key: MCHANGELOG-80
> URL: http://jira.codehaus.org/browse/MCHANGELOG-80
> Project: Maven 2.x Changelog Plugin
> Issue Type: New Feature
> Reporter: Simon Kitching
> Attachments: changelog_svn_revision.patch
>
>
> Currently, only selecting by-date is supported for Subversion. However
> subversion has a problem with date-selection in some cases.
> In particular, when CVS projects are imported into subversion, and the
> original commit date info is preserved during import, then all subversion
> select-by-date operations are broken for the repository. This is a known
> issue with subversion, and not likely to be fixed in the near future. The
> basic issue is that subversion maps a date to a revision-number by doing a
> binary-search across all its revisions, and assumes that the commit-date for
> revision N is before the commit-date for revision N+M. This is not true when
> external repos (CVS or other) are imported into subversion with original
> commit dates preserved.
> One example of a repository where this is a problem is *svn.apache.org*; all
> select-by-date is completely broken for the apache repo; always has been and
> will be until (if) a subversion release is made that has an additional
> "committed on" attribute for each commit, and changes made to svn to use an
> index on this property rather than its existing binary-search.
> It would therefore be *very* nice to be able to specify a subversion revision
> range, eg "from r100000 to HEAD" as the input to the report.
--
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
