Hi; I've run FindBugs for Lucene/Solr project. If you use Intellij IDEA you can group the warnings according to their importance. I've opened issues and attached patches for top level warnings/errors (and some others) that FindBugs found.
On the other hand I have another suggestion for Lucene/Solr project. When I develop or lead projects I use Sonar. It's so good and it runs really nice open source projects to analyze your code. FindBugs, PMD, Jacoco are just some of them. It also calculates the method complexities, LoC and etc. You can see a live example from here: https://sonar.springsource.org/dashboard/index/4824 I can be volunteer to integrate Sonar into Lucene/Solr project. Thanks; Furkan KAMACI 2014-03-16 11:01 GMT+02:00 Shawn Heisey <s...@elyograg.org>: > With the default settings in Eclipse, the Lucene/Solr codebase shows > over 6000 warnings. This is the case for both branch_4x and trunk. I'm > no expert, but this does seem a little excessive. If I were to take on > the task of reducing this number, what advice can the group give me? Is > there someone in particular that I should consider a resource for > inevitable dumb questions? > > I haven't done an exhaustive survey, but I would imagine that most of > them can be eliminated fairly easily. I'm fully aware that we may not > be able to eliminate them all. > > One problem with fixing warnings is that the resulting patch(es) would > be just as invasive as the recent work to move branch_4x to Java 7. > This would complicate any ongoing work, especially large-scale work that > is happening onchange-specific branches. > > A similar topic that may require a separate discussion: FindBugs. > > Thanks, > Shawn > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org > For additional commands, e-mail: dev-h...@lucene.apache.org > >
