[ http://jira.codehaus.org/browse/MPCHECKSTYLE-35?page=comments#action_44262 ]
Carlos Sanchez commented on MPCHECKSTYLE-35: -------------------------------------------- If you have such a huge report you shouldn't be using checkstyle or you should start with a smaller set of rules > Add option to break report into multiple files for large results > ---------------------------------------------------------------- > > Key: MPCHECKSTYLE-35 > URL: http://jira.codehaus.org/browse/MPCHECKSTYLE-35 > Project: maven-checkstyle-plugin > Type: Wish > Reporter: Jeff Jensen > > > For large projects, the load of the HTML report is unwieldy with the rule > violations. This particularly occurs when setting up on existing codebases > many rule violations. Not only does it take a long time to load, it is > overwhelming for team members to wade through this large page. This does not > help the effort of adoption. > Also, the current "workaround" is to greatly reduce the rule set to make > smaller results. But that is not optimal and prolongs the problem. Even > with a reduced ruleset, our checkstyle-report.html file is over 13M. > Suggested organization: > - The main page has the current Summary and Files sections. Each file > link loads a separate page, vs linking to a ref on the same page. > - Have an All on one page link that provides as is today (handy for > printing smaller lists if needed, and also for audits). > - If needed, have a config property that states which way to generate the > report all on one page or separate pages - that defaults to all on one page > so it maintains backwards compatibility. -- 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 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
