one thing not mentioned is that you can already just do ‘jbang run@jruby’ and run jruby directly if you wish.
At a time I looked into enabling more native jruby support so like jbang can run Java, jsh, groovy and kotlin add first class support for jruby and gems.
If someone interested and know about how to package ruby apps in a jar + addditional files that would be all doable.
And other option is how graalpy provided integration allowing use of //PIP to install packages.
We have all of the right tooling created to fetch jars from maven but no good tutorials on stitching it all together. Clearly that is step we should document better.
And for those following along, we keep the jbang configuration updated with every release so you know you're getting the most recent version.
one thing not mentioned is that you can already just do ‘jbang run@jruby’ and run jruby directly if you wish.
At a time I looked into enabling more native jruby support so like jbang can run Java, jsh, groovy and kotlin add first class support for jruby and gems.
If someone interested and know about how to package ruby apps in a jar + addditional files that would be all doable.
And other option is how graalpy provided integration allowing use of //PIP to install packages.
Just ping if interested :)