Because in CliClient.resume() we don't account for the case, when there is an exception in one of the async processing stages:

void resume() {
	...
	try {
		client.startAsync(state -> {
			printer.ifPresent(p -> p.print(state));
			if (!options.shouldSeedAfterDownloaded() && state.getPiecesRemaining() == 0) {
				runtime.shutdown();
			}
		}, 1000); // <-- CompletableFuture.w

There is a number of SporBugs static analysis warnings in the old parts of the Jenkinsfile Runner codebase. It is possible to see the warnings in the build log. Although there is no severe issues, it would be great to cleanup these warnings and then enforce SpotBugs checks during the build.

List of the current SpotBugs violations: https://ci.jenkins.io/job/jenkinsfile-runner/job/jenkinsfile-run

The tool fails when running without options. It would be better to print a message about the -help command in such case.

onenashev@LAPTOP-25K65LOS:/c/Users/Oleg/Documents/jenkins/demo/demo-jenkins-config-as-code$ java -jar jenkins-plugin-manager-1.0.2.jar
No .txt or .yaml file containing list of plugins to be downloaded entered.
No directory to download plugins entered. Will use defaul

Expected Behavior

I expect that arithmetic expression where there is no space between operands and operator can be parsed correct. E.g. (3*3) or (3*3) + 3

Current Behavior

Arithmetic expressions like (3*3) currently throw errors (like comparison contains Different DataTypes). Expressions like (3*3) + 3 are parsed like (3.0+3.0) wh