log-parser-1.11.0

• (new feature) #10 We now have an executable for the log-parser. You can perform a log parsing using the command line. For more information please read the section on Command-line Execution of the Log-Parser.
• (new feature) #127 You can now compare two LogData Objects. This is a light compare that checks that for a given key, if it is absent, added or changes in frequency.
• (new feature) #154 We have a data enrichment feature, where you can enrich the log data with additional information. For further details please refer to the section on Enriching Log Data.
• (new feature) #138 We now have the possibility of anonymizing log data during parsing. For more information please read the section on Anonymizing Data.
• (new feature) #117 You can now include the file name in the result of the analysis.
• (new feature) #141 You can now export a LogData as a table in a HTML file.
• (new feature) #173 You can now export a LogData as a JSON file.
• (new feature) #123 We now log the total number and size of the parsed files.
• #110 Moved to Java 11
• #169 We only keep one Parse Definition entry with the same title in a Parse Definition.
• #157 Search terms ar no longer a Map of key and Objects. Instead, they are now a map of Parse Definition Entry names and Hamcrest Matchers. This may cause compilation errors for those using the search & filter functions. For migration purposes please refer to the section on Defining a Search Term.
• #57 Assertions are no longer an implicit assert equal method. We now allow Hamcrest Matchers for asserting. This can be one or more matchers.
• #119 Cleanup of deprecated methods, and the consequences thereof.
• #137 We can now generate an HTML report for the differences in log data.
• #185 Resolved issue with deserializing unexpected objects in SDK Log entries..