Lilith 0.9.43

Changes

• Added ability to reconnect views after disconnect. All multiplex appenders are now creating a UUID upon startup and add that id to the logger context.
  To revert to the old behavior, i.e. one view for every single connection, you can disable usage of UUID in the configuration of the appender.
  
  <CreatingUUID>false</CreatingUUID>
  
  This was suggested by Joe.
• Added HTTP status codes 208, 226, 308, 420, 451, 508, 598 & 599.
• Added 'filter' command that filters all events of an input file that match a given condition into an output file. This is faster than filtering in Lilith itself since the UI isn't eating up CPU while filtering.
  
  This was suggested by Joe.
• Added command line option to specify a custom logback configuration.
• Added minimal logback configuration for command line commands.
• Added support for log4j2.
• Logback 1.0.12 introduced a change that broke LogbackShutdownServletContextListener.
  Implemented ContextHelper to be compatible with both 1.0.12 and lower.
• SLF4J 1.7.5, Logback 1.0.12, log4j 1.2.17, log4j2 2.0-beta5, Groovy 2.1.3, commons-io 2.4, commons-lang3 3.1, httpcore 4.2.4, httpclient 4.2.5, aspectj 1.7.2, jackson 2.2.0, jcommander 1.30, Spring 3.2.2.RELEASE, protobuf-java 2.5.0, jgoodies-looks 2.5.2, glazedlists 1.9.0, cglib 3.0, junit 4.11

Known Issues

• Flying Saucer related issues:
  • Selection in the HTML view is currently somewhat buggy, especially in case of scaled view.
    See Issue 79: SelectionHighlighter not compatible with ScalableXHTMLPanel
  • The first line of the message in HTML view is not properly indented if it starts with whitespace. You can see this effect by examining the event created by LogPinupLargeRunnable (executed via "Log ASCII"). The HTML created is actually correct.
    See Issue 125: <pre> ignores leading whitespace
  • Jumping to anchors is currently not supported so the navigation in help and details view isn't as good as it could be.
    See Issue 105: URLs with anchors
• Lilith may hang during startup while creating the preferences dialog. Just restart Lilith in that rare case.
  This is caused by bug #6995182 and I can't do anything about it.
  Sorry about it. It's a stupid Java-MediaTracker-ColorChooser-Bug with no workaround available.
  m(

Attention

This release changes detailsView.groovy in a way incompatible with previous versions!

If you switch back to a previous version, you must reset this file. Simply execute "Preferences" => "Troubleshooting" => "Reinitialize details view files." in that case.

Previous Versions

• 0.9.42.1
• 0.9.42
• 0.9.41
• 0.9.40
• 0.9.39
• 0.9.38
• 0.9.37
• 0.9.36