Page History

...

Note that in any case, unless you use hidden-classes or inverse-classloading to load your own copy of log4j separate from the geronimo copy, log4j will not automatically read any log4j.properties files you may have included in your classpath.

If you are building your own application

This example is taken from the apache directory plugin for geronimo, so the paths etc are adapted for that plugin.

...

1. Include the log4j.properties configuration file in an appropriate location in your plugin, say META-INF/log4j.properties
2. Unpack the log4j.properties file during plugin installation by including something like this in the pom.xml that generates geronimo-plugin.xml:

   Code Block
   <plugin> <groupId>org.apache.geronimo.buildsupport</groupId> <artifactId>car-maven-plugin</artifactId> ... <instance> <plugin-artifact> <copy-file relative-to="server" dest-dir="var/directory">META-INF/log4j.properties</copy-file> ... </plugin-artifact> </instance> </configuration> </plugin>

If you are deploying your app by some other means:

Copy the log4j.properties file by hand to the appropriate location such as var/my-app/log4j.properties. There is no need to include this file in your app.