Tim Jacomb

it is yes although it's not very user friendly, but most of Jenkins seems to use it for some reason so maybe best to stick to it. here's a link...

The api is just... bad But fine to keep the status quo and use JUL log4j2 is the most modern logger java has as far as I know with logback...

JUL has very limited parameters for the level specific methods, `logger.warn("")` etc only take very limited parameters. 99% of the time you end up having to do: logger.log(Level.WARN, "My message",...

I don't think anything should be there at all other than the message

no it's a CLI, try out some other CLI tools and see the output they give, a debug / verbose level log could maybe add some more information

can you take a look at the tests?

Breaking changes are fine here, ideally have an upgrade guide / command map table though. I would just include in PR and release notes, maybe README can link to it...

Available updates only works on plugin files not the jenkins war itself so it won't be too useful here. Not sure if it's intentionally excluded, most likely just not implemented.

I mean this CLI tool does not inspect your installed versions in any way, it just processes a `plugins.txt` file. > I ran into this today. To solve it I...

Hi You need to determine which truststore is being used by your Java installation and ensure it's updated with your internal cert, (or get a trusted cert via something like...