Community
Participate
Working Groups
The generic ECF logger spits out a lot of messages. Most of these might be useful to those first playing with ECF but they soon run into a barrage of noise which gets in the way of whatever the application's logging is doing. Can I suggest that we add two properties: ecf.log.info ecf.log.debug where if these are set (or set to a value, like 'true' or 'false'), they enable the output of Info messages or Debug messages from the ECF codebase? Clearly one can insert their own OSGi log service to bind it to the appropriate filtration, but 'filter all info' isn't the same as 'filter all info from ECF'. I'd suggest: showInfo = Boolean.parse(System.getProperty("ecf.log.info","false")); showDebug = Boolean.parse(System.getProperty("ecf.log.debug","false")); showWarn = Boolean.parse(System.getProperty("ecf.log.warn","true")); showError = Boolean.parse(System.getProperty("ecf.log.error","true")); That gives the user the opportunity to say which mechanism they should use. This could be placed in e.g. SystemLogService.doLog.
New tracing introduced in bug 472661. Much of the previous RSA logging has been removed in favor of the org.eclipse.ecf.services.remoteserviceadmin.DebugRemoteServiceAdminListener class.