maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bruno Marti (JIRA)" <>
Subject [jira] (MCHANGES-98) Add paging capatibility to changes report
Date Mon, 02 Jun 2014 05:57:10 GMT


Bruno Marti commented on MCHANGES-98:

Why not using footable-jquery [] and adding
it on html rendering?
I've added a little demo ZIP, which demonstrates pagination in a current changes-report.htm
as a result report

<link rel="stylesheet" type="text/css" href="footable.core.css"/>                  
<script type="text/javascript" src="jquery-1.11.1.min.js"></script>
<script type="text/javascript" src="footable.js"></script>
<script type="text/javascript" src="footable.paginate.js"></script>
<script type="text/javascript">
	$(function () {

<table class="bodyTable table table-striped table-bordered footable" border="0" data-page-size="5">
    <tr class="a">
        <td colspan="3">
            <div class="pagination pagination-centered hide-if-no-paging"></div>

> Add paging capatibility to changes report
> -----------------------------------------
>                 Key: MCHANGES-98
>                 URL:
>             Project: Maven Changes Plugin
>          Issue Type: Improvement
>          Components: changes.xml
>    Affects Versions: 2.0-beta-3
>            Reporter: Benjamin Bentmann
>         Attachments:
> 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

View raw message