#85 JETT logging should rely on Log4j (or some other modern logging library) instead of writing to System.err

[Aron Gombas]

It happens to us sometimes that we need to understand what happens in JETT internally in a production system. Currently we'd need to recompile the lib with DEBUG_TAG=true or DEBUG_GENERAL=true, and then rebuild our own application and then deal with the error stream. This isn't very realistic in production systems.

Why don't you just rebuild this to use log4j?

[Randy Gettman]

Aron,

I've checked in changes to use Log4j2 (2.9.0). I've changed all if (DEBUG) System.err.println statements to Log4j2 Logger calls, even adding some logging statements.

Yes, it was about time I used a logging framework.

This code is now checked in and it will be part of the next JETT build. Because Log4j2 2.4+ requires JDK 1.7+, I have now raised the requirement for using JETT to 1.7.

[Randy Gettman]

This was included in JETT 0.11.0, which was released on May 14, 2018.