...
- A default logging configuration is now bundled into OLE FS
- All logging is handled at runtime via Log4j
- Any logging added to the application from now on should use SLF4J
- As code gets updated, log4j logging statements should get replaced with SLFJ logging statements
- To This means logging will work out of the box without needing to create and configure log4j.
- You can still override the default log4j configuration if desired
- set the property
ole.fs.log4j.override=true - create the file
~/.kuali/ole/fs/log4j.propertiescontaining your custom settings
- set the property
- All logging is handled at runtime via Log4j
- Any logging added to the application from now on should use SLF4J
- As code gets updated, log4j logging statements should get replaced with SLFJ logging statements
Properties
Property | Default Value | Description |
|---|---|---|
olefs.configuration | None | If this system property is set, properties are loaded from the location it points to. Properties supplied here, override internal properties |
ole.fs.runtime.property.expansion=true/false | true | If true, property expansion is performed at runtime instead of at build time. The resource |
ole.fs.log4j.override=true/false | false | Set this to true if you want to override the default log4j.properties supplied with the application. This also allows you to alter the log4j configuration at runtime without restarting the application. The log4j.properties file supplied here is monitored by a background thread. It is automatically reloaded when changes are detected. |