JMH 1.18

[Aleksey Shipilev]

Hi,

JMH 1.18 is released with a single, but very important bugfix:

The benchmark metadata was written out and read back in platform encoding. Which
means, if you generate the benchmarks on one machine with platform encoding A,
take the JAR to another machine, and run with platform encoding B -- it might
fail if A != B. The same can happen if source/target encoding for Java is A
(e.g. set in build file), but the platform encoding is B. There are code paths
that use A, and some that use B. The truly sad part is that it can fail
*silently*, if benchmark names are in ASCII (as they usually are), but the
@Params are in non-ASCII. You will never know this until you try to print param
value.

Fixed:
  https://bugs.openjdk.java.net/browse/CODETOOLS-7901910

Thanks,
-Aleksey