GuardLogStatementJavaUtil, GuardDebugLogging and GuardLogStatement should be merged.
The first one says "JavaUtil" in it's name, but will actually report against other logging libraries such as Log4J.
The second one is for some reason only looking at debug logs, and the name says so, but can actually be configured to look at all log levels (and makes sense to do so).
The third one is pretty much the same as the first one.
We should simply have a GuardLogStatementRule to work on all supported libraries (commons-logging, Log4J, SLF4J, java logging) with a common configuration.
Also of note, all rules state that the default value for logLevels is [] (it's not, but it's configured at runtime), and the same happens with guardsMethods. We should take the chance to fix this.
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4