JOGAMP PROJECTS NEED TO USE FINDBUGS AND OTHER STATIC CHECKING TOOLS
I recently ran the java findbugs tool over my project and it picked up a boat-load of really bad stuff in the jogamp project files.
Now, I am sure the teams are really overwhelmed when they peer review and check source code into the baseline.
And I am sure you guys use something like Jenkins to perform automatic builds for these projects.
But, I would advise the teams to turn on as many of the static checking tools (jenkins plugins) as possible, and seriously consider asking the team members to resubmit their source after they fix the serious and egregious bad practices contained in the source.
The teams might even consider running the tools and generating some internal change requests after reviewing the results.
Keep up the great work and please don't take my recommendation as criticism for your hard work and great efforts.
From: gouessej [via jogamp] [mailto:ml-node+[hidden email]]
Sent: Wednesday, December 30, 2015 16:09 To: Etkins, Dave (HGR) <[hidden email]> Subject: Re: JOGAMP PROJECTS NEED TO USE FINDBUGS AND OTHER STATIC CHECKING TOOLS
We could use Sonar with its plugins for Findbugs and PMD.