Errorprone for Java

Contents

  1. Integration with IDEs
  2. Running the checks
  3. Patching
    1. Preparation
    2. Apply the fixes
    3. Test, cleanup
    4. Prepare to submit

Error Prone is a static analysis tool for Java that catches common programming mistakes at compile-time. See https://errorprone.info/

ICU4J runs it in CI for each pull request to prevent problems from being introduced, and to periodically generate a report, posted at https://github.com/unicode-org/icu, under the “Quality Reports (main branch)” → “Java static analysis” section).

Integration with IDEs

See https://errorprone.info/docs/installation

Running the checks

There are currently two CI checks for errorprone. One is executed for each PR, and fails if a problem is detected. The other one generates a full report, and does not fail. The result is posted on the project GitHub page, under “Quality Reports.”

Here is how you run the test that runs in CI:

mvn clean test -DskipTests -DskipITs -P errorprone

And here is how to run the full test that produces reports in html, tsv, and md formats.

# Run the checks mvn clean test -DskipTests -DskipITs \ -l /tmp/errorprone_all.log -P errorprone-all # Generate reports in html, tsv, and md formats mvn exec:java -f icu4j/tools/errorprone_report/ \ -DlogFile=/tmp/errorprone_all.log -P errorprone_report # Make sure it says "BUILD SUCCESS" tail /tmp/errorprone_all.log

Patching

See https://errorprone.info/docs/patching.
But we will summarize here how to use it from Maven, for ICU4J.

Note: This is the patching mechanism provided by errorprone itself. But there are (of course) other ways, for example an IDE.
For example I had good results with Eclipse, enabling a certain check, then asking Eclipse to fix all instances.

Note: this patching is not necessarily perfect. Always check, visually and by running all tests.

Preparation

  1. Edit the errorprone.cfg file in the root of the ICU repo.
  2. Add two more flags: -XepPatchLocation:IN_PLACE and -XepPatchChecks:<IssueType>, on separate lines.
    For example:
    -XepPatchLocation:IN_PLACE -XepPatchChecks:UnusedMethod

Apply the fixes

Run the errorprone report generation step:

mvn clean test -DskipTests -DskipITs -l /tmp/errorprone_all.log -P errorprone-all

If errorprone knows how to patch the kind of issue you specified, it will update the files.

Note: the patches will not always apply cleanly.

Keep an eye on warnings or errors, you might have to fix some problems “by hand.”

Test, cleanup

Re-format:

mvn spotless:apply

Test:

mvn package

Visually inspect the changed files (git diff or a GUI git client are handy here). Compare with the initial errorprone report.

Prepare to submit

  1. Update errorprone.cfg to declare the issue you just fix as an error.
    That way it will prevent it from coming back in the future.
    • Change -XepPatchChecks:<IssueType> to -Xep:<IssueType>:ERROR.
      In our example -XepPatchChecks:UnusedMethod to -Xep:UnusedMethod:ERROR.
    • Move the -Xep:<IssueType>:ERROR together with the other :ERROR tags if not there, keeping that block of tags sorted.
    • Remove -XepPatchLocation:IN_PLACE.
  2. Check that everything is fine
    • Run all the errorprone checks (see “Running the checks”) to see that all the issues of that type are fixed.
    • Run a regular build with testing:
      mvn clean package
  3. You might have to go back to “Test, cleanup” if something fails.
  4. Finally, create a PR, commit, push, send for review.

Back to top

© 2016 and later: Unicode, Inc. and others. License & terms of use: http://www.unicode.org/copyright.html

Edit this page on GitHub.

This site uses Just the Docs, a documentation theme for Jekyll.