[ 
https://issues.apache.org/jira/browse/SOLR-16878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17741742#comment-17741742
 ] 

ASF subversion and git services commented on SOLR-16878:
--------------------------------------------------------

Commit 61e5a5b78b89fe0241e1c72184d764993b4e8c57 in solr's branch 
refs/heads/branch_9x from Houston Putman
[ https://gitbox.apache.org/repos/asf?p=solr.git;h=61e5a5b78b8 ]

SOLR-16878: Remove unnecessary line

(cherry picked from commit e1f8a6ac75e56d5bfbc5493d99b94ee60f4113d4)


> Include Lucene JUL logs with Solr logging
> -----------------------------------------
>
>                 Key: SOLR-16878
>                 URL: https://issues.apache.org/jira/browse/SOLR-16878
>             Project: Solr
>          Issue Type: Improvement
>      Security Level: Public(Default Security Level. Issues are Public) 
>          Components: logging
>    Affects Versions: 9.0
>            Reporter: Houston Putman
>            Assignee: Houston Putman
>            Priority: Blocker
>             Fix For: 9.3
>
>          Time Spent: 2h 20m
>  Remaining Estimate: 0h
>
> Starting with Lucene 9.1.0, Lucene now logs certain warnings and errors using 
> Java Util Logging (JUL). Upgrade notes: 
> https://lucene.apache.org/core/9_1_0/MIGRATE.html
> For Solr's Log4J setup to include these logs, we must follow Log4J's JUL 
> instructions and  set 
> {{-Djava.util.logging.manager=org.apache.logging.log4j.jul.LogManager}} when 
> starting Solr. We will also need to include the {{log4j-jul}} jar in lib-ext 
> with the other logging jars.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org
For additional commands, e-mail: issues-h...@solr.apache.org

Reply via email to