You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by "Stefan Seelmann (JIRA)" <ji...@apache.org> on 2015/05/01 16:52:06 UTC
[jira] [Updated] (DIRSTUDIO-1042) Fix logging system
[ https://issues.apache.org/jira/browse/DIRSTUDIO-1042?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stefan Seelmann updated DIRSTUDIO-1042:
---------------------------------------
Description:
The logging system is broken. There seem to be multiple issues.
1. When starting Studio a message like this is printed:
{noformat}
log4j:WARN No appenders could be found for logger (org.apache.directory.api.ldap.model.schema.parsers.AbstractSchemaParser).
log4j:WARN Please initialize the log4j system properly.
log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info.
{noformat}
In API and ApacheDS bundles we use slf4j. Currently we add slf4j-log4j12 binding and log4j bundles. However there is no log4j.properties configuration.
One approach is to keep log4j add a Fragement-Host for log4j that contains the log4j.properties.
Another approach is to remove log4j and add our own slf4j binding that forwards logs to Eclipse/OSGI log service.
2. When running SWTBot tests lot of server logs are printed ot stdout.
was:
The logging system is broken. There seem to be multiple issues.
1. When starting Studio a message like this is printed:
{noformat}
log4j:WARN No appenders could be found for logger (org.apache.directory.api.ldap.model.schema.parsers.AbstractSchemaParser).
log4j:WARN Please initialize the log4j system properly.
log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info.
{noformat}
2. When running SWTBot tests lot of server logs are printed ot stdout.
> Fix logging system
> ------------------
>
> Key: DIRSTUDIO-1042
> URL: https://issues.apache.org/jira/browse/DIRSTUDIO-1042
> Project: Directory Studio
> Issue Type: Bug
> Reporter: Stefan Seelmann
> Fix For: 2.0.0-M9
>
>
> The logging system is broken. There seem to be multiple issues.
> 1. When starting Studio a message like this is printed:
> {noformat}
> log4j:WARN No appenders could be found for logger (org.apache.directory.api.ldap.model.schema.parsers.AbstractSchemaParser).
> log4j:WARN Please initialize the log4j system properly.
> log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info.
> {noformat}
> In API and ApacheDS bundles we use slf4j. Currently we add slf4j-log4j12 binding and log4j bundles. However there is no log4j.properties configuration.
> One approach is to keep log4j add a Fragement-Host for log4j that contains the log4j.properties.
> Another approach is to remove log4j and add our own slf4j binding that forwards logs to Eclipse/OSGI log service.
> 2. When running SWTBot tests lot of server logs are printed ot stdout.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)