TRUNK-6271: Log4JCompatibilityTest fail on github workflow

[ManojLL]

Description of what I changed

added logging levels to logger

Issue I worked on

see https://issues.openmrs.org/browse/TRUNK-6271

Checklist: I completed these to help reviewers :)

• My IDE is configured to follow the code style of this project.

  No? Unsure? -> configure your IDE, format the code and add the changes with git add . && git commit --amend

• I have added tests to cover my changes. (If you refactored
  existing code that was well tested you do not have to add tests)

  No? -> write tests and add them to this commit git add . && git commit --amend

• I ran mvn clean package right before creating this pull request and
  added all formatting changes to my commit.

  No? -> execute above command

• All new and existing tests passed.

  No? -> figure out why and add the fix to your commit. It is your responsibility to make sure your code works.

• My pull request is based on the latest changes of the master branch.

  No? Unsure? -> execute command git pull --rebase upstream master

[wikumChamith]

@dkayiwa, @ibacher can you take a look at this?

[ibacher]

This fundamentally subverts what this test is actually testing s this isn't really a great solution to the problem...

[ManojLL]

@ibacher what about adding logger for "Log4JCompatibility" in log4j2.xml file. By adding the "Log4JCompatibility" logger configuration, 'log4j' can capture all log messages for this logger and send them to the console. This allows our test to capture and check the log messages produced during the test.

<Logger name="Log4JCompatibility" level="ALL" additivity="false"> <AppenderRef ref="CONSOLE" /> </Logger>

[wikumChamith]

@dkayiwa, @ibacher, is this the right time to remove support for Log4j 1.x?

openmrs-core/api/src/test/java/org/openmrs/logging/Log4JCompatibilityTest.java

Lines 23 to 26 in 489168f

	/**
	* Class to ensure that we maintain some level of compatibility with Log4J 1.X
	* At some point in the future, this compatibility guarantee should be removed.
	*/

[ibacher]

@wikumChamith No. We haven't actually removed the Log4J 1.x API from any modules that use it.

@ManojLL The Log4JCompatibility logger is just something that exists for the purposes of this test. Adding it to the file makes it more permanent than it needs to be.

[ManojLL]

@ibacher initializing the log4j logger after the log4j2 memory appender starts, that cause to set the compatinilityLogger level to OFF.

[dkayiwa]

In the meantime, in order to have our builds pass on GitHub pull requests, i have reverted log4jVersion from 2.24.1 to 2.22.1
We can upgrade it again after this is done.