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

• Type: Improvement
• Status: In Progress
• Priority: Minor
• Resolution: Unresolved
• Fix Version/s: 2.1.0
• Assignee: Roger Lee Whitcomb
• Reporter: Roger Lee Whitcomb
• Created: 01/Mar/18 17:15
• Updated: 01/Nov/23 02:17

Description

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.