few comments here: - the log4j version with the is...
# kotlin-logging
o
few comments here: • the log4j version with the issue is not old (it was on latest). as a fix 2.15.0 was published • kotlin-logging was using log4j only for testing (it uses slf4j and users can pick which logging framework they wish). so using kotlin-logging does not cause this issue for users. However, to be on the safe side version 2.1.16 of kotlin-logging was published today with test dependency of log4j 2.15.0, if anyone wish to upgrade.
🙏 1