Error Prone

It’s common for even the best programmers to make simple mistakes. And
sometimes a refactoring which seems safe can leave behind code which will never
do what’s intended.

We’re used to getting help from the compiler, but it doesn’t do much beyond
static type checking. Using Error Prone to augment the compiler’s type
analysis, you can catch more mistakes before they cost you time, or end up as
bugs in production. We use Error Prone in Google’s Java build system to
eliminate classes of serious bugs from entering our code, and we’ve
open-sourced it, so you can too!

Error Prone …

hooks into your standard build, so all developers run it without thinking