2.3.0-RC1
---------
o Prints help information if no arguments were given to the import tool.
o Root cause like stack traces are printed for unexpected errors, regardless of the value of
  --stacktrace that user supplied. That option still controls whether or not stack traces should
  be printed for common errors, which are usually accompanied a more descriptive explanation.
o Includes meta data about the store and stored transactions in diagnostics logging during startup.

2.3.0-M01
--------
o Added ability to skip duplicate nodes, i.e. multiple nodes with the same ID in the same id space.
  Maximum total number of bad entries (nodes and relationships) during an import is still controlled
  using --bad-tolerance=<max bad entries>. Skipping of bad relationships/nodes can be enabled/disabled
  individually with --skip-duplicate-nodes and --skip-bad-relationships.

2.2.6
-----
o Stacktraces are printed for any unexpected exception, even if --stacktrace isn't supplied.
  --stacktrace can still be used to print stack trace for known exceptions.
o Adds --ignore-empty-strings for ignoring empty quoted strings, instead of those values
  ending up as properties with empty string values

2.2.5
-----
o No longer ignores --multiline-field option

2.2.4
-----
o Empty files are now handled gracefully and no longer infinitely loop
o Multiline fields are now enabled by default

2.2.3
-----
o Prints summary in the end of how many entities where imported.

2.2.2
-----
o Ability to skip duplicate nodes (nodes w/ duplicate input ids within the same id space).
  For this --skip-duplication-nodes as well as --skip-bad-relationships have been added.
  Number of bad entries to tolerate collectively is still controlled using --bad-tolerance
o Improved user feedback on common and import errors and user mistakes like forgetting to
  specify input files or leaving out mandatory header information etc. In some cases also
  points out a place in the manual for further information about a particular problem.
o Removes the --bad option which previously could specify the location and file name of
  the log containing bad input entries after an import. Now that log file will always be
  <into>/bad.log
o Input file names can now contain regular expressions and therefore match multiple files.
  Matching files will be correctly ordered according to any and all numbers found in their file names.
o Ability to allow/disallow multi-line fields, i.e. fields containing new-line characters.
  This to have a better default defense against missing end quotes.
  Default is to disallow multi-line fields. While being a change in behavior, this option
  will most likely result in less surprising handling of fields missing end quotes..

2.2.1
-----
o Ability to specify input encoding (using --input-encoding)
