Gary Gregory <garydgreg...@gmail.com> schrieb am So., 6. Nov. 2016 um 19:00 Uhr:
> The whole post is interesting. Sounds like a fork is inevitable. So much > work though... > There already is a fork. See [1] Benedikt [1] https://github.com/spotbugs/spotbugs > > Gary > > On Nov 6, 2016 9:32 AM, "Stian Soiland-Reyes" <st...@apache.org> wrote: > > > See > > https://mailman.cs.umd.edu/pipermail/findbugs-discuss/ > > 2016-November/004321.html > > > > In particular the author is not happy about the BCEL integration: > > > > > The other major reasons for the FindBugs current bad state: > > > > > > 1) The code is very complex, has "organically grown" over a decade, is > > > not documented and has poor public interfaces. Most of the code > consists > > > of the very low level bytecode related stuff, tightly coupled with the > > > ancient BCEL library, which doesn't scale and is not multi-thread safe. > > > No one enjoys maintaining this code, at least not me. I see no future > > > for FindBugs with the BCEL approach, and see no way to get rid of it > > > without investing lot of effort, and without breaking every detector > and > > > possibly many 3rd party tools. This is the biggest issue we have with > > > FindBugs today, and most likely the root cause for all the evil. This > > > code can't be fixed, it must be rewritten. > > > > ..but the main problem seems to be lack of maintaners. > > > > > > -- > > Stian Soiland-Reyes > > http://orcid.org/0000-0001-9842-9718 > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > > For additional commands, e-mail: dev-h...@commons.apache.org > > > > >
