configuration log to avoid warn from jetty annotations parse

Tested with debug remote on a server.

The approach is working fine, just that server is showing a lot more warnings than eclipse:

9948 scanned from multiple locations
8400 unique
7073 unique when swapping source and target

69 pointing to different folder -> all
org.adempiere.extend_6.2.0.201903241716.jar
org.adempiere.base_6.2.0.201903241716.jar

7004 pointing to same folder

____________________

after setting the tracelevel in idempiere.properties down to 2913 warnings
all warnings before loading the properties
two more folders in the warnings:
org.eclipse.equinox.app_1.4.0.v20181009-1752.jar
org.eclipse.jetty.apache-jsp_9.4.14.v20181114.jar

I guess changing the log level to SEVERE is not the most recommendable solution, just a workaround until jetty solves that reported issue 2072.

reopening - commit 2b34bd3 is working in eclipse, but not in server

Hi, closing the ticket as there is a current easy workaround using idempiere.properties to set the log level.

Also I tagged the ticket as Potential Idea - because this can be interesting if we want to implement a more detailed way to manage logs.

Regards,

Carlos Ruiz

yeb. tracking that stuff here

BTW, I think the extend plugin could be deleted - or at least disconnected by default from core and just keep it like the ui.zk.example plugin.

This would be about deleting the callout registered in column Test.Integer and disabling that plugin.

WDYT?