Minimize exposure of JDK internals
- Dominant language
- Java
- Stars
- 7.2k
- Forks
- 820
- Avg merge
- 5h 9m
- Merged PRs (30d)
- 50
Description
Have you considered adopting a module declaration?
It would allow minimizing the exposure of JDK internals to errorprone, which would surface any abuse of these internals by other third-party libraries/annotation processors.
```
--add-exports jdk.compiler/com.sun.tools.javac.api=com.google.errorprone
--add-exports jdk.compiler/com.sun.tools.javac.file=com.google.errorprone
--add-exports jdk.compiler/com.sun.tools.javac.main=com.google.errorprone
--add-exports jdk.compiler/com.sun.tools.javac.model=com.google.errorprone
--add-exports jdk.compiler/com.sun.tools.javac.parser=com.google.errorprone
--add-exports jdk.compiler/com.sun.tools.javac.processing=com.google.errorprone
--add-exports jdk.compiler/com.sun.tools.javac.tree=com.google.errorprone
--add-exports jdk.compiler/com.sun.tools.javac.util=com.google.errorprone
--add-opens jdk.compiler/com.sun.tools.javac.code=com.google.errorprone
--add-opens jdk.compiler/com.sun.tools.javac.comp=com.google.errorprone
```
Contributor guide
Assessment
This issue has not been assessed yet.