maven-issues mailing list archives

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

    [ https://jira.codehaus.org/browse/MCHANGES-98?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=347360#comment-347360
] 

Bruno Marti commented on MCHANGES-98:
-------------------------------------

Why not using footable-jquery [http://fooplugins.com/plugins/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

*usage:*
{code}
<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 () {
		$('.footable').footable();
	});
</script>
{code}

{code}
<table class="bodyTable table table-striped table-bordered footable" border="0" data-page-size="5">
<thead>
    <tr class="a">
        <th>Version</th>
        <th>Date</th>
        <th>Description</th>
    </tr>
</thead>
<tfoot>
    <tr>
        <td colspan="3">
            <div class="pagination pagination-centered hide-if-no-paging"></div>
        </td>
    </tr>
</tfoot>
<tbody>
...
{code}


> Add paging capatibility to changes report
> -----------------------------------------
>
>                 Key: MCHANGES-98
>                 URL: https://jira.codehaus.org/browse/MCHANGES-98
>             Project: Maven Changes Plugin
>          Issue Type: Improvement
>          Components: changes.xml
>    Affects Versions: 2.0-beta-3
>            Reporter: Benjamin Bentmann
>         Attachments: footable-pagination.zip
>
>
> 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
(v6.1.6#6162)

Mime
View raw message