You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@harmony.apache.org by "Tim Ellison (JIRA)" <ji...@apache.org> on 2008/01/03 13:51:35 UTC
[jira] Closed: (HARMONY-1997) [classlib]adopt CheckStyle to follow
junit best practice
[ https://issues.apache.org/jira/browse/HARMONY-1997?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tim Ellison closed HARMONY-1997.
--------------------------------
> [classlib]adopt CheckStyle to follow junit best practice
> --------------------------------------------------------
>
> Key: HARMONY-1997
> URL: https://issues.apache.org/jira/browse/HARMONY-1997
> Project: Harmony
> Issue Type: Improvement
> Components: Classlib
> Reporter: Tony Wu
> Assignee: Tim Ellison
> Priority: Trivial
> Attachments: junitBP.xml, junitBP.xml, junitBP.xml
>
>
> There are many violations found by Mark's tools(Harmony-1960). To fix and avoid them, I suggest to use CheckStyle as a Eclipse plugin, which will highlights all possiable violate lines in your editor windows.
> I post my configuration here as an initial. It must be not very precise, you can customize it by yourself. Any bug report are welcome.
> HOW TO
> 1,Install CheckStyle, you can find it at http://eclipse-cs.sourceforge.net/ .
> 2,After that you can find an item named checkstyle in your eclipse menu-windows-preferences, click the new button and then import my configuration.
> 3,In the properties of a project, there is also an item named checkstyle, you can enable checkstyle for your project here. remember to select the right configuration you just import.
> 4,If you get an out of memory error, you can do something in its exclude options. for example, exclude files not opened in the editor.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.