Raul, I'm afraid it will produce 100500 false-positive warnings. I think we need to investigate what will be generated by FB tune it and then decide to include it or not into maven build.
Or may be we could have it as optional step (it is possible?). On Fri, Nov 13, 2015 at 11:32 PM, Raul Kripalani <[email protected]> wrote: > I'd prefer to plug it into the Maven build: > https://gleclaire.github.io/findbugs-maven-plugin/. > > *Raúl Kripalani* > PMC & Committer @ Apache Ignite, Apache Camel | Integration, Big Data and > Messaging Engineer > http://about.me/raulkripalani | http://www.linkedin.com/in/raulkripalani > http://blog.raulkr.net | twitter: @raulvk > > On Fri, Nov 13, 2015 at 4:02 PM, Sergi Vladykin <[email protected]> > wrote: > > > It absolutely does make sense. Of course it will not find complex bugs > but > > it is pretty good at spotting stupid mistakes. > > > > Time ago I used to run Eclipse plugin for FindBugs, I believe something > > alike should exist for Idea as well. > > > > Sergi > > > > 2015-11-13 17:49 GMT+03:00 Alexey Kuznetsov <[email protected]>: > > > > > Igniters, > > > > > > What do you think about checking Ignite code base with Findbugs ( > > > http://findbugs.sourceforge.net)? > > > > > > Does it make sense? > > > > > > Maybe someone will try? > > > > > > Thoughts? > > > > > > -- > > > Alexey Kuznetsov > > > > > > -- Alexey Kuznetsov GridGain Systems www.gridgain.com
