Unleash the power of Java - JBang Lets Students, Educators and Professional Developers create, edit and run self-contained source-only Java programs with unprecedented ease.
As far as I can tell jbang always runs with -classpath, even if the resolved "script" is an executable jar. The logical thing to do would seem to be to spot (or have the user specify) the fact that it is executable, and just ignore the dependencies or not bother resolving them. Instead we get a long classpath with the executable jar at the start. Is there a reason for that?
dsyer
commented
1 week ago
As far as I can tell jbang always runs with -classpath, even if the resolved "script" is an executable jar. The logical thing to do would seem to be to spot (or have the user specify) the fact that it is executable, and just ignore the dependencies or not bother resolving them. Instead we get a long classpath with the executable jar at the start. Is there a reason for that?
Example from the
TestRuntest cases:where
would have been just fine (and less prone to mismatched dependency resolution expectations between jbang and the jar author).