Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Doc: project readme could explain the benefits v.s. findbugs #19

Open
RichardBradley opened this issue Jan 29, 2014 · 0 comments
Open

Comments

@RichardBradley
Copy link

It is possible to run findbugs on a scala codebase, since findbugs acts on bytecode.
See e.g. https://github.com/sbt/findbugs4sbt
It also seems to work tolerably well; I found a few bugs in my scala project (unclosed file handles) this way. However it does generate masses of false positives mostly around class and method naming conventions.

Is alacs a reimplementation of the findbugs bytecode scanner plus a ruleset optimised for Scala?

Is that expected to offer benefits not achievable by a project that just took the findbugs codebase and worked on Scala specific scanners and tweaked the existing findbugs scanners to reduce Scala specific false positives?

I assume that you've already considered this, but it seems likely to be a FAQ -- the project README could address this issue directly?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant