[
https://issues.apache.org/jira/browse/MCHANGES-98?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov closed MCHANGES-98.
----------------------------------
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.
> Add paging capatibility to changes report
> -----------------------------------------
>
> Key: MCHANGES-98
> URL: https://issues.apache.org/jira/browse/MCHANGES-98
> Project: Maven Changes Plugin
> Issue Type: Improvement
> Components: changes.xml
> Affects Versions: 2.0-beta-3
> Reporter: Benjamin Bentmann
> Priority: Major
> Attachments: footable-pagination.zip, screenshot-1.jpg
>
>
> 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 was sent by Atlassian JIRA
(v7.6.3#76005)
