jbang export now has a sub-command to export your jbang script/app to
a maven repo.
This allows jbang scripts/apps to be used like any other maven dependencies by
i.e. classic maven and gradle projects.
For it to work you need to publish the repo using tools that understand maven repositories.
One such tool is https://jitpack.io which provides a build service that exposes github,
gitlag, etc. git repositories as maven repositories.
To get jitpack to understand jbang projects you need to put a jitpack.yml in the root of the project
with content like this:
before_install:
- curl -Ls https://sh.jbang.dev | bash -s - app setup
install:
- ~/.jbang/bin/jbang export mavenrepo --force -O target -Dgroup=$GROUP -Dartifact=$ARTIFACT -Dversion=$VERSION hello.java
- mkdir -p ~/.m2/repository
- cp -rv target/* ~/.m2/repository/This should enable some interesting usecases for jbang script and applications :)
Breaking change
Since jbang export now have subcommands, instead of flags you will need to use jbang export local instead of jbang export from past versions of jbang.
Bug Fixes
- Fixed template init naming validation (#c7b0b593, closes #790)
- be able to launch editors with space in name (#800) (#b2b06628)