Fix: Avoid potential null dereference with log4j loggers
authorAlexandre Montplaisir <alexmonthy@efficios.com>
Thu, 19 May 2016 18:49:06 +0000 (14:49 -0400)
committerMathieu Desnoyers <mathieu.desnoyers@efficios.com>
Thu, 19 May 2016 19:50:52 +0000 (15:50 -0400)
Coverity warns that the return of LogManager.getCurrentLoggers()
can contain null elements. Add an explicit null check to skip those.

Signed-off-by: Alexandre Montplaisir <alexmonthy@efficios.com>
Signed-off-by: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>

No differences found
This page took 0.024986 seconds and 4 git commands to generate.