Project: mule
Issue MULE-7920: SimpleLog mode should have custom logic for locating configuration file
OOTB, log4j2 looks for its configuration file using this algorithm: * Scan all classpath looking for file log4j2-test.xml * If not found, repeat looking for log4j2.xml When Mule is running with its default logging infrastructure, this logic is overridden so that the search is not performed on all classpath but: * First on the application classpath * If not found on the domain classpath * If not found, on the configuration folder When running in simple log mode, all of Mule's custom logic is not applied and we fallback to log4j2 default implementation, which causes issues because we cannot guarantee that any other jar in the classpath includes such a file, causing the wrong file to be picked up. When runnning in simple mode, log separation should be disabled but our custom search algorithm should still be applied. Additionally, in both cases we should generate a log line informing the path in which we found the file.
Story points: 3