Tako Schotanus
Tako Schotanus
The idea is that user impact at first is as close to zero as possible. Mainly to detect if the new system causes any backward compatibility issues. For the user...
> on windows the symbolic linking also works ? JBang already needs those to work. The default jdk that gets added to your path is a link (a Junction to...
That flag doesn't let you keep the compiled classes, you need to pass `-Djbang.build.keepclasses=true` for that. (we should probably document that, I only used it for debugging but it seems...
I'm not very well-versed with JBang in GitHub actions, so I'll let @maxandersen take a look at this, but I wanted to mention at least that we _do_ actually support...
> Maybe related to [#475 (comment)](https://github.com/hatoo/oha/issues/475#issuecomment-2084627504) I think it's even better explained by this issue: #364 isn't it?
Aha, so possibly we simply need to delete any .jsa files whenever we rebuild the jar, right?
The important part being that whatever we choose as the name for an os and an arch would always work regardless of what the author of the artifact called it,...
Changed title to be less dramatic :-) It's only `jbang init` that has this issue after all. Also cleaned up the issue text a bit.
Yeah, definitely think this could be a plugin. The _only_ thing I can think if that could cause a bit of duplication of code is the part where you say...
> These are reasons to extract those core logic as library. Definitely