FindBugs project in its current form is dead
mailman.cs.umd.edu
FindBugs project in its current form is dead
1–10 of 121 posts
Re: FindBugs project in its current form is dead
#2This is sad, I've enjoyed using findbugs when I was doing java.
Fingers crossed that this can lead to a rebirth of the project.
Re: FindBugs project in its current form is dead
#3What a shame - it caught a few bugs in my code and has definitely made me a better programmer.
One of the reasons is that the code is hard to maintain with most open source contributions being small improvements. How have other open source projects handled large scale refactors? Is it as simple as someone creating something new from scratch and then duplicating functionality? Are there examples of large open source projects that have had ground up rewrites?
Re: FindBugs project in its current form is dead
#4A million downloads, commercial deployments by 3rd parties, and basically no contributions coming in. The status quo of the open-source model. They should start selling it to companies to finance their own work on it. Or encourage others interested in static analysis to do the same.
Re: FindBugs project in its current form is dead
#5Interestingly, the spirit of the FindBugs project lives on in the development of languages like Rust and Swift, considering the purpose of the FindBugs project is to fix inherent flaws in Java, e.g. not having a way to determine whether something will be null, or not telling you whether you checked whether something will be null at runtime, etc.
Re: FindBugs project in its current form is dead
#6Interestingly, the spirit of the FindBugs project lives on in the development of languages like Rust and Swift, considering the purpose of the FindBugs project is to fix inherent flaws in Java, e.g. not having a way to determine whether something will be null, or not telling you whether you checked whether something will be null at runtime, etc.
Clang static analyzer is another great tool that didn't exist back then.
Re: FindBugs project in its current form is dead
#7What a shame. I work for a fortune 100 company that enables findbugs on all projects by default. I cannot fathom how many serious issues it's prevented.
Re: FindBugs project in its current form is dead
#8I don't have a Twitter account, so maybe I'm missing something about the difficulty here. But the author spent paragraphs describing how the fate of this major thing is largely in the hands of Bill Pugh, he can't reach Bill Pugh via email, maybe his email is expired, etc. etc. can someone please help contact him via phone or twitter or whatever?
Why not just create a twitter account and do it yourself? WTF?
edit: presumably one of the downvoters is working right this minute to contact Bill Pugh via Twitter and put him in touch with the author, because that totally makes sense
Re: FindBugs project in its current form is dead
#9What a shame. I work for a fortune 100 company that enables findbugs on all projects by default. I cannot fathom how many serious issues it's prevented.
[deleted]
Re: FindBugs project in its current form is dead
#10What a shame - it caught a few bugs in my code and has definitely made me a better programmer. One of the reasons is that the code is hard to maintain with most open source contributions being small improvements. How have other open source projects handled large scale refactors? Is it as simple as someone creating something new from scratch and then duplicating functionality? Are there examples of large open source p…
The nice thing about FindBugs is that you can, e.g., automatically run it in a Jenkins pipeline.
Just for ad-hoc analysis in Java IntelliJ's code inspector IMO works quite well. It's also available in the community edition, so all of that code is open source: https://www.jetbrains.com/help/idea/2016.2/code-inspection.h...