[ https://issues.apache.org/jira/browse/SOLR-8330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15030101#comment-15030101 ]
Uwe Schindler commented on SOLR-8330: ------------------------------------- Hi, I had an idea a minute ago how to prevent incorrectly declared loggers. In root's build.xml we have the source-patterns ant task (that greps on source files for "violations"). We could add a regular expression for finding "bad loggers" and fail "ant validate" because of that. We can commit this afterwards, I can work on some regexes to detect this (some combinations of positive/negative patterns). > Restrict logger visibility throughout the codebase to private so that only > the file that declares it can use it > --------------------------------------------------------------------------------------------------------------- > > Key: SOLR-8330 > URL: https://issues.apache.org/jira/browse/SOLR-8330 > Project: Solr > Issue Type: Sub-task > Affects Versions: Trunk > Reporter: Jason Gerlowski > Assignee: Anshum Gupta > Labels: logging > Fix For: Trunk > > Attachments: SOLR-8330.patch, SOLR-8330.patch, SOLR-8330.patch, > SOLR-8330.patch, SOLR-8330.patch > > > As Mike Drob pointed out in Solr-8324, many loggers in Solr are > unintentionally shared between classes. Many instances of this are caused by > overzealous copy-paste. This can make debugging tougher, as messages appear > to come from an incorrect location. > As discussed in the comments on SOLR-8324, there also might be legitimate > reasons for sharing loggers between classes. Where any ambiguity exists, > these instances shouldn't be touched. -- This message was sent by Atlassian JIRA (v6.3.4#6332) --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org