[
https://issues.apache.org/jira/browse/SOLR-8676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15337206#comment-15337206
]
ASF subversion and git services commented on SOLR-8676:
-------------------------------------------------------
Commit c20b41fe6b1d023a5bdf30e39afa1b470597bcc5 in lucene-solr's branch
refs/heads/branch_5x from [~mkhludnev]
[ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=c20b41f ]
SOLR-8676: keep LOG4J_CONFIG in solr.cmd
> 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
> Fix For: 5.6, 6.1, 5.5.2, master (7.0), 6.0.2
>
> Attachments: SOLR-8676.patch, SOLR-8676.patch, verifying SOLR-8676.txt
>
>
> 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-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
