You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by "Jeff Jensen (JIRA)" <ji...@codehaus.org> on 2005/06/24 15:39:52 UTC
[jira] Created: (MPCHECKSTYLE-35) Add option to break report into multiple files for large results
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: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Closed: (MPCHECKSTYLE-35) Add option to break report into multiple files for large results
Posted by "Carlos Sanchez (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MPCHECKSTYLE-35?page=all ]
Carlos Sanchez closed MPCHECKSTYLE-35:
--------------------------------------
Assign To: Carlos Sanchez
Resolution: Won't Fix
Now there's a summary page that should help, although don't fix the problem with the full list of problems taking too much time to be generated. My suggestion is reduce the number of rules until lower the number of errors.
> 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
> Assignee: Carlos Sanchez
>
>
> 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: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Commented: (MPCHECKSTYLE-35) Add option to break report into multiple files for large results
Posted by "Carlos Sanchez (JIRA)" <ji...@codehaus.org>.
[ 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: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org