GoogleContainerTools / GoogleContainerTools/jib
Set up Error Prone check to prevent use of native Gradle and Maven loggers
Open
area/jib-gradle-plugin
area/jib-maven-plugin
cleanup
priority: p4
- Dominant language
- Java
- Stars
- 14.5k
- Forks
- 1.5k
- PR merge metrics
- No merged PRs in 30d
Description
Using the native Gradle logger was probably why [our deprecation messages were overwritten](https://github.com/GoogleContainerTools/jib/pull/2109#issuecomment-555174722).
We should be careful not to make use of the native Maven or Gradle loggers. We can prevent misuse in `ProjectProperties` by just using `consoleLogger`. But it is very easy to accidentally use the native loggers in Maven mojos and Gradle tasks. Unfortunately, now I realized we had used the native loggers when printing deprecation notices.
Contributor guide
Assessment
This issue has not been assessed yet.