This content has been marked as final. Show 4 replies
PVM can use JDK logging (java.util.logging) or log4j. When the first message is logged, PVM logging will make the selection with following procedure:
1. If a logging.properties resource is found on the classpath (using the context classloader), then JDK logging will be used and that file will be used to initialize the JDK logging.
2. If log4j is found on the classpath, then log4j will be used. The check for log4j will be done by checking availability of class org.apache.log4j.LogManager with the context classloader.
3. If none of the above, JDK logging will be used.
The check is *not* done based on log4j.properties but on the presence of org.apache.log4j.LogManager. Keep in mind that this should be in the context classloader path and that in this same path, *no* logging.properties should be present.
Any idea how to do that with maven?
or with tomcat...
uhmmmm.... maven is a build management tool.... Tomcat is a servlet engine... I do not understand your question.... Or at least not the relation to your 'problem'...