EZID Ships with a log4j.properties File

[nate-hook]

Good Afternoon,

I would like to request that the log4j.properties file be removed from your build if possible.

The shipped log4j.properties file is clashing with our logging properties file and causing our application to spew a ton of unwanted log messages.

Thank you for your time,

Regards,

Nate

[mbjones]

@hooknc Your application has complete control over how log4j is initialized. I assume you figured this out when you reported this issue, but I am documenting this for historical reference. See the 'Default Initialization Procedure' section of the log4j manual for the procedures that you can use to set up your configuration to ignore the file that we ship. The log4j.properties file is shipped as a default debug configuration for the ezid library, but is easily ignored, so we will continue to ship the file. Some of the techniques you can use (from the manual), include:

• Set the log4j.configuration system property to the URL of the properties file you want to use. The preferred way to specify the default initialization file is through the log4j.configuration system property. In case the system property log4j.configuration is not defined, then the name "log4j.properties" is used, and searched for on the classpath (see next approach)
• Place a log4j.properties file on your application classpath before the ezid jar. This properties file will be loaded and take precedence, and you can define any logging directives you need. This approach can be tricky to debug because classpath evaluation in an app is complicated. It's much more straightforward to use the log4j.configuration system property above.