You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Mikhail Khludnev (JIRA)" <ji...@apache.org> on 2016/05/28 09:07:12 UTC

[jira] [Commented] (SOLR-8676) It's not possible to use a different log4.properties file on windows

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

Mikhail Khludnev commented on SOLR-8676:
----------------------------------------

[~thelabdude], do you have an any objections? I see that {{LOG4J_CONFIG}} set to empty for non-example launch during SOLR-6833. 

> It's not possible to use a different log4.properties file on windows
> --------------------------------------------------------------------
>
>                 Key: SOLR-8676
>                 URL: https://issues.apache.org/jira/browse/SOLR-8676
>             Project: Solr
>          Issue Type: Bug
>    Affects Versions: 5.4.1
>            Reporter: Kristine Jetzke
>            Assignee: Mikhail Khludnev
>         Attachments: SOLR-8676.patch
>
>
> It's currently not possible to change the location of the log4j.properties file on windows. The value of {{LOG4J_CONFIG}} always gets replaced with the default value {{server\resources\log4j.properties}}. Thus, this file inside the server directory needs to be changed after every update.
> See attached patch for a fix. Unfortunately, I couldn't figure out why {{LOG4J_CONFIG}} was set to empty. I tested manually that logging still works when running an example so I hope that this line is really just obsolete.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org