directory-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <wikidi...@apache.org>
Subject [Directory Wiki] Update of "LoggingPlan" by nickfaiz
Date Wed, 27 Jul 2005 21:15:32 GMT
Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Directory Wiki" for change notification.

The following page has been changed by nickfaiz:
http://wiki.apache.org/directory/LoggingPlan

------------------------------------------------------------------------------
  
  == Logging as an embedded server vs Logging as a standalone server ==
  
- We should not distribute default logging configuration files - for example, log4j.properties
- in the jar distribution of the server. There's a high chance it will conflict with applications
which use the same logging system and list the server as a dependency. This simply means that
the maven jar:jar goal should not include a log4j.properties, it can be renamed to apacheds-log4j.properties
instead.
+ We should not distribute default logging configuration files - for example, log4j.properties
- in the jar distribution of the server. There's a high chance it will conflict with applications
which use the same logging system and list the server as a dependency. This simply means that
the maven jar:jar goal should not include a log4j.properties, it can be renamed to apacheds-log4j.properties
instead. This means that, during development, IDEs will be able to use logging effectively
but that, after being placed on a maven repo., parent applications won't be worried by it.
  
  When starting the server in standalone mode, i.e. as a jar, a System property should be
applied "log4j.configuration" to indicate that apacheds-log4j.properties (see http://logging.apache.org/log4j/docs/manual.html#defaultInit).
I have yet to test this with nlog4j will update this later, having done so. A wrapper script,
server-standalone.sh/server-standalone.bat could make this easy.
  

Mime
View raw message