[
http://jira.codehaus.org/browse/MCHANGELOG-63?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_98043
]
Dennis Lundberg commented on MCHANGELOG-63:
-------------------------------------------
1. This part of the patch will not work, since the methods getEndTag() and
getStartTag() are not available in Maven-SCM, even after SCM-294 was applied.
2. This has been fixed by MCHANGELOG-59.
3. When I apply this part things look really strange for a subversion
changelog, where you can have several files changed in one commit. They end up
one after the other without formatting.
The code for creating the heading has been refactored into just one method in
ChangeLogReport, if you want to have another go at creating a patch.
> Tag-based reports have new headers, SCM-comments with newlines get linebreaks
> in HTML, lay-out update on changelog-report
> -------------------------------------------------------------------------------------------------------------------------
>
> Key: MCHANGELOG-63
> URL: http://jira.codehaus.org/browse/MCHANGELOG-63
> Project: Maven 2.x Changelog Plugin
> Issue Type: Improvement
> Affects Versions: 2.0
> Reporter: Roland Asmann
> Priority: Minor
> Attachments: maven-changelog-plugin-2.0-CFC-20070330.patch
>
>
> Several updates that made the lay-out of the sites change:
> - Reports based on tags don't show the message for ranges, but have own
> headers and messages now. This change needs the updates I made to SCM
> (http://jira.codehaus.org/browse/SCM-294)!
> - Newlines in SCM-comments are printed with line-breaks now.
> - Removed the paragraph-tags around every single file-entry (didn't like the
> way it looked).
--
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
