The 3.12.x branch did not make the leap to Log4j 2.x API, and was just released again this week. The use of reload4j as a drop-in replacement for the log4j library allows the 3.12.x branch to be released using a supported/patched logging library.
The PR builds and starts up; but is not tested. I would like confirmation that the PSC figures this is a good idea before spending any further tie on this proposed change.
To me seems a good idea to use a supported/patched logging library like reload4j which has the same API as log4j 1.2 as there are quite a few users still using GeoNetwork 3.12.
The 3.12.x branch did not make the leap to Log4j 2.x API, and was just released again this week. The use of reload4j as a drop-in replacement for the log4j library allows the 3.12.x branch to be released using a supported/patched logging library.
The PR builds and starts up; but is not tested. I would like confirmation that the PSC figures this is a good idea before spending any further tie on this proposed change.