You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Benjamin Bentmann (JIRA)" <ji...@codehaus.org> on 2008/02/06 17:40:30 UTC
[jira] Created: (MCHANGES-98) Add paging capatibility to changes
report
Add paging capatibility to changes report
-----------------------------------------
Key: MCHANGES-98
URL: http://jira.codehaus.org/browse/MCHANGES-98
Project: Maven 2.x Changes Plugin
Issue Type: Improvement
Components: changes-report
Affects Versions: 2.0-beta-3
Reporter: Benjamin Bentmann
The current report generation does not scale well for projects with a large release history because one ends up with a very long HTML page. Preferable would be to introduce a configuration parameter like "releasesPerPage" that the mojo could use to split up the change log onto several web pages.
Usually, such paging should only apply to web content and not something like PDF or other print-related formats.
--
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
[jira] Commented: (MCHANGES-98) Add paging capatibility to changes
report
Posted by "Bruno Marti (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MCHANGES-98?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=227823#action_227823 ]
Bruno Marti commented on MCHANGES-98:
-------------------------------------
Does anybody care about this? There is no Assignee yet.
I would really appreciate this feature
> Add paging capatibility to changes report
> -----------------------------------------
>
> Key: MCHANGES-98
> URL: http://jira.codehaus.org/browse/MCHANGES-98
> Project: Maven 2.x Changes Plugin
> Issue Type: Improvement
> Components: changes-report
> Affects Versions: 2.0-beta-3
> Reporter: Benjamin Bentmann
>
> The current report generation does not scale well for projects with a large release history because one ends up with a very long HTML page. Preferable would be to introduce a configuration parameter like "releasesPerPage" that the mojo could use to split up the change log onto several web pages.
> Usually, such paging should only apply to web content and not something like PDF or other print-related formats.
--
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