[jira] [Updated] (DIRSERVER-1350) Support changing log4j configuration for SiRunner-launched ApacheDS instances

["Emmanuel Lecharny (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/DIRSERVER-1350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Emmanuel Lecharny updated DIRSERVER-1350:
-----------------------------------------

    Fix Version/s:     (was: 2.0.0)
    
> Support changing log4j configuration for SiRunner-launched ApacheDS instances
> -----------------------------------------------------------------------------
>
>                 Key: DIRSERVER-1350
>                 URL: https://issues.apache.org/jira/browse/DIRSERVER-1350
>             Project: Directory ApacheDS
>          Issue Type: Improvement
>    Affects Versions: 1.5.4
>            Reporter: Aleksander Adamowski PZU
>            Assignee: Kiran Ayyagari
>
> See the discussion at http://www.mail-archive.com/dev@directory.apache.org/msg23067.html for initial details.
> It seems that currently the log4j configuration is forcibly hardcoded inside the ApacheDS JARs and a log4j configuration file placed on test classpath doesn't influence Apache DS components' logging.
> It makes it extremely hard to diagnose problems with launching and shutting down the embeddded Apache DS instance used for tests (http://cwiki.apache.org/DIRxSRVx11/42-using-apacheds-for-unit-tests.html).
> There should be a way to override the logging configuration of all ApacheDS components using a log4j configuration file placed on the unit test classpath.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira