Thank you Jinghai, Taher, I put the same in both lucene and solr components (Solrs relies on Lucene) and of course there are no drawbacks
I must say I was not able to reproduce the "error" locally. But I anyway propose to commit in the 2 plugins to reassur people who could else wonder. And it may also be useful at some point, who knows... Jacques Le 19/05/2017 à 15:08, Taher Alkhateeb a écrit :
The master build.gradle file should not point to any plugins On Fri, May 19, 2017 at 1:10 PM, Shi Jinghai <[email protected]> wrote:Hi Jacques, In ${ofbiz.home}/build.gradle, adding solr.log.dir and solr.log.level can remove this error message, i.e.: def jvmArguments = ['-Xms128M', '-Xmx1024M', '-Dsolr.log.dir=runtime/logs', '-Dsolr.log.level=INFO'] I tried define jvmArguments in ${ofbiz.home}/plugins/solr/build.gradle, it doesn't work. Kind Regards, Shi Jinghai -----邮件原件----- 发件人: Jacques Le Roux [mailto:[email protected]] 发送时间: 2017年5月19日 17:55 收件人: [email protected] 主题: Lucene and Solr loggin Hi, I noticed this error in trunk demo error.log 2017-05-16 03:05:38,898 |0.0.0.0-startStop-1 |StartupLoggingUtils |E| Missing Java Option solr.log.dir. Logging may be missing or incomplete. It's thrown by https://github.com/apache/lucene-solr/blob/master/solr/ core/src/java/org/apache/solr/servlet/StartupLoggingUtils.java I can't see nothing at https://localhost:8443/solr/#/~logging Is that really an issue in our case? It seems there is not much we can do about it. Thanks Jacques
