Improve YADE log configuration

Current Situation
The YADE log4j configuration currently configures 3 loggers:

• root logger
  • logs to stdout
  • logline includes thread name, priority, time, Java class and linenr, java methodname, message
  • can output log levels higher than info
• JadeReportLogHTML
  • logs to an html file in java.io.tempdir
  • cannot output log levels higher than info because the code uses a special logger
• JadeReportLog
  • logs to a .log file in java.io.tempdir
  • logline includes time (with lots of padding), message
  • cannot output log levels higher than info because the code uses a special logger

IMHO this is a bad configuration because:

• stdout log is more verbose than a file log
• stdout log prints the thread name, but there is only one thread
• file log cannot be easily configured to a higher log level
  • How can a customer send an informational log to SOS in case of problems?

The log formats should be open for discussion. I suggest the following

Desired Behaviour

The YADE log4j configuration configures 3 loggers:

• root logger
  • logs to stdout
  • logline includes priority, time, message
  • can output log levels higher than info
• JadeReportLogHTML
  • logs to an html file in java.io.tempdir
  • can output log levels higher than info
• JadeReportLog
  • logs to a .log file in java.io.tempdir
  • logline includes priority, time, Java class and linenr, java methodname, message
  • can output log levels higher than info