Due to an addition of a Logger.getlogger call in snakeyaml library after v1.18 the log4j2 initialization is broken since the call should not be made until the logging manager is set via system property.
In case of no resolution upstream the log4j2 initialization code will have to be cleverly reworked to detect the log4j2 extension without triggering snakeyaml library.
There were no major changes since version 1.18 so the downgrade should have no negative effect.
Due to an addition of a
Logger.getloggercall in snakeyaml library after v1.18 the log4j2 initialization is broken since the call should not be made until the logging manager is set via system property.Issue is pending upstream: https://bitbucket.org/asomov/snakeyaml/issues/461/trouble-with-loggergetlogger-call-in
In case of no resolution upstream the log4j2 initialization code will have to be cleverly reworked to detect the log4j2 extension without triggering snakeyaml library.
There were no major changes since version 1.18 so the downgrade should have no negative effect.