Magic jbang edit

jbang edit yourfile.java now assumes your IDE has one of the jbang plugins installed (see https://jbang.dev/ide).
Since jbang edit install and run vscodium by default if you simply use jbang edit things will just work.

If you want the old behavior (which is great with emacs, vi, etc.) then just enable sandbox using (-b) jbang edit -b yourfile.java

JBang will based on the arguments you pass take an educated guess on which folder you want to open based on the source file.
It will look at package/directory names, for common editor markers (.vscode,.project,.idea, etc) and build files (pom.xml, build.gradle,etc) to find the best place to open an IDE.

Module cleanup

In previous versions we introduced support for building modular applications. You indicate to JBang with a //MODULE command or by having a module-info.java file then JBang will automatically switch to using modulepaths over classpath. This release continues to clean things up and make it easier to use.

Export jlink

jbang export jlink is now an option. Allowing you write a jbang app/script and export it as an application that has the Java runtime embedded within it.

Changelog

🐛 Fixes

• 0a5a45a exlude naming.ldap from module list and support package in package name

🛠 Build

• 8d81b9e fix formatting

• 1e13a0b [patch]

Contributors

We'd like to thank the following people for their contributions:
Max Rydahl Andersen