Age | Commit message (Collapse) | Author | Files | Lines |
|
Optimize the log output
Issue-ID: SDC-3232
Signed-off-by: JulienBe <julien.bertozzi@intl.att.com>
Change-Id: I50cfb7119b1e9087d3e2db56a81fe47df4ad6254
|
|
Due to issues in the log4j files, the tests can't be started and crash
Issue-ID: SDC-3223
Signed-off-by: sebdet <sebastien.determe@intl.att.com>
Change-Id: I77909d98c716a8a232f5cc8ae8baddebb4ee581f
|
|
Signed-off-by: amohamad <a.mohamad@queensu.ca>
Issue-ID: SDC-3051
Upgrade from the vulnerable log4j 1.x to log4j 2.13.1
Add a log4j version property in sdc-main pom.xml
Add two maven dependencies to respective child pom.xml
Change name of log4j .properties and .xml config files
to reflect log4j2 naming
Update the configuration files to the totally new
log4j 2 config syntax
Replace PropertyConfigurator with LoggerContext
Remove the abandoned log4j.lf5.util.ResourceUtils
Signed-off-by: amohamad <a.mohamad@queensu.ca>
Change-Id: Ie0f141eb2e0337ee5b63b61dc1395ccd8040558d
|