[jira] [Updated] (KAFKA-9940) Command "jmh.sh -h " doesn't work. The description in readme is wrong

["jiamei xie (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/KAFKA-9940?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

jiamei xie updated KAFKA-9940:
------------------------------
    Summary: Command "jmh.sh -h " doesn't work. The description in readme is wrong  (was: Command "jmh.sh -h " doesn't work)

> Command "jmh.sh -h " doesn't work. The description in readme is wrong
> ---------------------------------------------------------------------
>
>                 Key: KAFKA-9940
>                 URL: https://issues.apache.org/jira/browse/KAFKA-9940
>             Project: Kafka
>          Issue Type: Bug
>          Components: build, documentation
>            Reporter: jiamei xie
>            Priority: Major
>
> It is said "To view all options run jmh with the -h flag." in https://github.com/apache/kafka/blob/trunk/jmh-benchmarks/README.md. But it doesn't work with the following error:
> /jmh.sh -h running gradlew :jmh-benchmarks:clean :jmh-benchmarks:shadowJar in quiet mode If this is not your first run and there is nothing changed, you can skip this build stage by ./jmh.sh skip-build ... Building project 'core' with Scala version 2.12.11 Building project 'streams-scala' with Scala version 2.12.11 gradle build done running JMH with args [-h] Exception in thread "main" java.lang.NoSuchMethodError: joptsimple.OptionDescriptor.options()Ljava/util/Collection;         at org.openjdk.jmh.runner.options.OptionFormatter.lineFor(OptionFormatter.java:62)         at org.openjdk.jmh.runner.options.OptionFormatter.format(OptionFormatter.java:51)         at joptsimple.OptionParser.printHelpOn(OptionParser.java:342)         at joptsimple.OptionParser.printHelpOn(OptionParser.java:328)         at org.openjdk.jmh.runner.options.CommandLineOptions.showHelp(CommandLineOptions.java:457)         at org.openjdk.jmh.Main.main(Main.java:46) JMH benchmarks done
> The different version of
> jopt used in KAFKA and JMH is the root cause. KAFKA uses jopt 5.0.4 while
> JMH uses jopt 4.6. You can get the jopt change logs from http://jopt-simple.github.io/jopt-simple/changes.html



--
This message was sent by Atlassian Jira
(v8.3.4#803005)