[
https://issues.apache.org/jira/browse/PIVOT-1032?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16452885#comment-16452885
]
Roger Whitcomb commented on PIVOT-1032:
---------------------------------------
Work on UnusedImports errors:
Sending core/src/org/apache/pivot/beans/BXMLSerializer.java
Sending core/src/org/apache/pivot/collections/Queue.java
Sending core/src/org/apache/pivot/collections/Stack.java
Sending
core/src/org/apache/pivot/text/AttributedStringCharacterIterator.java
Sending core/src/org/apache/pivot/text/CharSpan.java
Sending core/src/org/apache/pivot/util/CalendarDate.java
Sending core/src/org/apache/pivot/util/Time.java
Sending core/test/org/apache/pivot/util/test/CharUtilsTest.java
Sending core/test/org/apache/pivot/util/test/ImmutableIteratorTest.java
Sending demos/src/org/apache/pivot/demos/million/LargeData.java
Sending tests/src/org/apache/pivot/tests/CheckedListViewTest.java
Sending tests/src/org/apache/pivot/tests/HyperlinkButtonTest.java
Sending tutorials/src/org/apache/pivot/tutorials/KitchenSink.java
Sending
tutorials/src/org/apache/pivot/tutorials/bxmlexplorer/FakeWindowSkin.java
Sending tutorials/src/org/apache/pivot/tutorials/lists/ListButtons.java
Transmitting file data ...............done
Committing transaction...
Committed revision 1830111.
> 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 Whitcomb
> Assignee: Roger Whitcomb
> Priority: Minor
> 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
(v7.6.3#76005)