[
https://issues.apache.org/jira/browse/SOLR-549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Henri Biestro updated SOLR-549:
-------------------------------
Attachment: solr-log4j.patch
Added target 'dist-log4j' in build.xml to optionally compile the log4j adapter
as a jar named 'apache-solr-log4j-1.3-dev'; if the jar in in the classpath,
log4j enabled logging is loaded.
The target also copies the produced jar into the tests/lib and adds it to the
tests classpath.
Note that log4j.1.2.15.jar must be added in the lib directory.
> Enable configurable logging (jul or log4j)
> ------------------------------------------
>
> Key: SOLR-549
> URL: https://issues.apache.org/jira/browse/SOLR-549
> Project: Solr
> Issue Type: Improvement
> Affects Versions: 1.3
> Reporter: Henri Biestro
> Attachments: solr-log4j.patch, solr-log4j.patch
>
>
> java.util.logging does not allow to easily create a self-sufficient 'war'
> with respect to logging configuration.
> The java.util.logging.LogManager used by the application is always created by
> the container and is thus only configurable through the container;
> furthermore, if one already uses say log4j in a webapp that embeds Solr, it
> does not even seem possible to re-route jul logging into log4j just by
> configuration.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
