Tako Schotanus

So there's two additional issues here @maxandersen : - if you depend on the compiler automatically picking up files then you can't run `Foo.java` if that file is remotely located....

There is indeed something wrong. First of all the fact that jbang choses the very generic name "jbang-catalog". Second I noticed that if you run two `jbang catalog add ...../jbang-catalog.json`...

> if you rm -rf ~/.jbang/cache/jars/httpd*, then you'll see info tools still returns the path to the resolved httpd jar: Actually that's always the case, you could do the same...

I still feel that `--resolve` is not a good option, we're already "resolving", all artifacts get downloaded. The thing that the option would do is to build any scripts that...

Completely, there it's a black box, it's something that's done completely transparently. You just end up with artifacts in your MAVEN_REPO. Except for the time it might take the first...

> and it works just nice: Btw you can also simply do `jbang eu.maveniverse.maven.mima:cli:2.4.4` (or :LATEST of course). And you can easily create an alias for that or install it...

@maxandersen well the original issue is still open and this PR is at least an intent towards a solution. But I haven't looked at this since last time it was...

Still not marked as ready :-) I'm just not 100% happy with it, even though it's a pretty nice feature.

No, this is not for the catalog, it's just that if someone wants to create an alias to run `jbang run/build --fresh` or `jbang run/build --offline` it would be nice...

Perhaps I misunderstood that issue, but I thought it to mean that it didn't automatically update to the latest version of the app. I assumed there's nothing in the alias...