You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@pivot.apache.org by "Roger Lee Whitcomb (Jira)" <ji...@apache.org> on 2021/06/30 03:40:00 UTC

[jira] [Commented] (PIVOT-1032) Implement "checkstyle" for builds and make changes to bring code into better compliance

    [ https://issues.apache.org/jira/browse/PIVOT-1032?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17371788#comment-17371788 ] 

Roger Lee Whitcomb commented on PIVOT-1032:
-------------------------------------------

Reduce the number of files to do a "checkstyle" on (basically just the "core" classes and not demos, tutorials, etc.).

Sending        build.xml
Transmitting file data .done
Committing transaction...
Committed revision 1891156.


> Implement "checkstyle" for builds and make changes to bring code into better compliance
> ---------------------------------------------------------------------------------------
>
>                 Key: PIVOT-1032
>                 URL: https://issues.apache.org/jira/browse/PIVOT-1032
>             Project: Pivot
>          Issue Type: Improvement
>            Reporter: Roger Lee Whitcomb
>            Assignee: Roger Lee Whitcomb
>            Priority: Minor
>             Fix For: 2.1.0
>
>         Attachments: 1032.diffs.txt
>
>
> I thought it would be interesting, in addition to the "trim-whitespace" task already implemented, to do some sort of "checkstyle" processing to evaluate all the code to see where there might be changes to make the code more robust and a better example of "canonical" Java style.
> I hesitate to expect that we could address everything (or indeed whether we *should*), but there might be things that would make the code better and easier to read and maintain, and wouldn't take much effort.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)