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
7073 unique when swapping source and target
69 pointing to different folder -> all
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:
I guess changing the log level to SEVERE is not the most recommendable solution, just a workaround until jetty solves that reported issue 2072.
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.
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.