(a) +1 for sure.
STREAMS-348: Create coding guidelines document for website
STREAMS-349: Maven plugin that can validate all classes have a sensible javadoc
header
STREAMS-350: Bring codebase into compliance with requirement for sensible
javadoc headers.
(b) +1 I think.
I agree with
(1) We could start with a bare minimum ground rules For FindBugs and refine
those as we move along.
(2) CheckStyle is a good idea -
- do we wanna 2 spaces or 2 tabs as beginning of each line, my
personal pref is 2 spaces (and no tabs)
On Mon, Oct 24, 2016 at 1:20 PM, Timothy Spann
That makes a lot of sense.
Maybe run FindBugs, PMD and CheckStyle.
I had 2 things in mind that we need to work in tandem with adding/improving
functionality in Streams.
(a) Remove author info from all code that has it, and add sensible JavaDocs
for each class
(b) Now that we are officially Java 8, minimize Guava API use and migrate
most Guava stuff to Java 8
