Reminds me of the time I told GitHub's Copilot to fix an issue. The first step was 90% there. Oh that's good! Then I spent 3 days (because I was determined to do the full 100% using AI) in that same loop you described before giving up and fixing the last 10% myself. :-)

But seriously, jpm simply follows the basic idea of npm where you maintain a list of dependencies for a project and have those dependencies stored locally in the same folder as the rest of the project's files. Under the hood resolving of dependencies is still done by Maven, no wheel is reinvented.

Two months ago, when I asked for feedback on Reddit (see www.reddit.com/r/java/comme...) several comments were along the line of "npm sucks! therefore so does your tool!". Now I don't know about npm sucking, but I know jpm doesn't suck 😜

Or if you want to use the original Gist:

jbang --deps com.fasterxml.jackson.core:jackson-databind:2.19.0 --java 25 gist.github.com/nipafx/bb980...

Politicians (and unfortunately a large part of the population) won't do anything unless it starts to affect them personally. Ukraine is far away and "not my problem" for them.

I've been helping Max for years now with JBang, so I agree that it is a lovely tool! But at the same time I'm also the author of Jpm, because I noticed that sometimes I wanted something simpler, more composable and with a bit more freedom to do things my way instead of the JBang way. :-)

JBang is an all-in-one solution for dealing with lots of issues that plague the Java ecosystem and one of its goals is to make working with Java as easy as possible. Jpm just does the depency bit, trying to be a more composable solution in the *nix way. Disclaimer, I'm a dev on both projects.