hangc0276 opened a new pull request, #16775:
URL: https://github.com/apache/pulsar/pull/16775
### Motivation
When running `bin/bookkeeper shell cookie_update` command, we get the
following exception.
```
$ bin/bookkeeper shell cookie_update -h
JMX enabled by default
Exception in thread "main" java.lang.NoSuchMethodError:
com.beust.jcommander.JCommander.usage(Ljava/lang/StringBuilder;)V
at org.apache.bookkeeper.tools.framework.Cli.setupCli(Cli.java:142)
at org.apache.bookkeeper.tools.framework.Cli.<init>(Cli.java:53)
at org.apache.bookkeeper.tools.framework.Cli.runCli(Cli.java:243)
at org.apache.bookkeeper.tools.common.BKCommand.apply(BKCommand.java:64)
at
org.apache.bookkeeper.tools.cli.helpers.BookieShellCommand.runCmd(BookieShellCommand.java:46)
at org.apache.bookkeeper.bookie.BookieShell.run(BookieShell.java:2235)
at org.apache.bookkeeper.bookie.BookieShell.main(BookieShell.java:2326)
```
The reason is that in BookKeeper 4.12.0, it depends on the `com.beust.
commander` version `1.48`, however, in Pulsar, we depend on the `com.beust.
commander` version `1.78`. The Pulsar depends version overrides the
BookKeeper's depends version.
However, `com.beust. commander` 1.78 version's interface has been changed,
which leads to the BookKeeper shell command can't be executed.
In BookKeeper 4.12.1, it upgrades the `com.beust. commander` version to 1.78
in https://github.com/apache/bookkeeper/pull/2523. So we can upgrade BookKeeper
dependency from 4.12.0 to 4.12.1 to solve this bug.
### Modification
Upgrade the BookKeeper version from 4.12.0 to 4.12.1
### Documentation
Check the box below or label this PR directly.
Need to update docs?
- [ ] `doc-required`
(Your PR needs to update docs and you will update later)
- [ ] `doc-not-needed`
(Please explain why)
- [ ] `doc`
(Your PR contains doc changes)
- [ ] `doc-complete`
(Docs have been already added)
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
