I have a .jar file (foo.jar, for instance) that we can't alter that contains a commons-logging.properties file (that redirects to JDK14Logging) and relies on an external commons-logging.jar file for it's logging. This, I believe is set to simply output to stdout which isn't very helpful.
We have a different logging system (log4J if it matters) that we are using, and would prefer to use. Is it possible to have an external properties file (sitting local to the foo.jar) that 'overrides' the one inside foo.jar?
I'm aware that SLF4J should work, as should editing the .jar in 7zip and 'recompiling' so to speak, but I feel that the first creates an extra dependency on a Jar (as requires bringing one into the environment) and the latter creates a dependency on someone to make the same edits we made to foo.jar to foo2.jar when/if we are provided with that when/if I have left the project.
Is this possible without editing the jar or SLF4J?? Or do I need to bite one of the aforementioned bullets?