-
Notifications
You must be signed in to change notification settings - Fork 7
Open
Description
There are two possible approaches:
- Add abstraction into Error Prone to become independent of javac as described in Run checks in Eclipse google/error-prone#11
- Build a bridge that translates from ECJ AST into javac classes and ensure Error Prone accepts those
We need to figure out what is the better strategy to go with. Having Error Prone integrated directly with ECJ would be nice because we are using ECJ as well in the Bazel Language Server (Eclipse and VS Code)
Error Prone is currently integrated in the Bazel Java Compiles via ErrorPronePlugin
/**
* A plugin for BlazeJavaCompiler that performs Error Prone analysis. Error Prone is a static
* analysis framework that we use to perform some simple static checks on Java code.
*/
public final class ErrorPronePlugin extends BlazeJavaCompilerPlugin {..}eperret
Metadata
Metadata
Assignees
Labels
No labels