build(deps): Make JBang script actually use Enola's brand new shiny M…

…aven repo distro
enola-dev · Feb 7, 2025 · 4e38518 · 4e38518
1 parent 79a07ef
commit 4e38518
Show file tree

Hide file tree

Showing 4 changed files with 12 additions and 10 deletions.
diff --git a/docs/dev/jbang.md b/docs/dev/jbang.md
@@ -18,20 +18,17 @@
 
 # JBang
 
-Java developers (not end-users) can use Enola via [JBang](https://www.jbang.dev/).
+Java developers (not end-users) can also use Enola via [JBang](https://www.jbang.dev/).
 
 [`learn/jbang`](https://github.com/enola-dev/enola/tree/main/learn/jbang)
 has an example project illustrating how this works; clone and go there, and then:
 
-1. `tools/maven/install.bash`
 1. `cd learn/jbang`
 1. `./jbang hello.java` will run an example using Enola
 1. `./jbang edit --sandbox --open=code hello.java` opens an IDE
 
-<!-- TODO Improve JBang integration:
-        1. Build Enola on JitPack, and remove the need for step #1.
-        2. Move `learn/jbang` out into a separate Git repo?
-(But then how to test it in CI?
-A Monorepo is very nice for that.
-Perhaps just write a script to automagically extract (copy) it into a small repo?
+<!-- TODO Move `learn/jbang` out into a separate Git repo?
+
+(But then how to test it in CI? A Monorepo is very nice for that.
+Perhaps just write a script to automagically extract (copy) it into a small repo?)
 -->
diff --git a/docs/dev/setup.md b/docs/dev/setup.md
@@ -89,6 +89,7 @@ If you do still want to try, here's how to manually install what the development
 
         sudo apt update
         sudo apt install golang-go
+        go install github.com/bazelbuild/bazelisk@latest
 
 You should now be able to proceed as above (but without requiring _Docker)._
 

diff --git a/java/pom.xml b/java/pom.xml
@@ -3,9 +3,13 @@
   xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
   <modelVersion>4.0.0</modelVersion>
 
+  <!-- This POM is currently not actually used to build this project (which uses Bazel as build tool).
+        This is really only here to get version bumps from Dependabot & Renovate bots (because that's "convenient").
+        The published POM of this project is entirely generated by Bazel, from its deps, NOT this file. -->
+
   <groupId>dev.enola</groupId>
   <artifactId>enola</artifactId>
-  <version>1.0.0-SNAPSHOT</version>
+  <version>0.0.0-SNAPSHOT</version>
   <packaging>jar</packaging>
 
   <properties>

diff --git a/learn/jbang/hello.java b/learn/jbang/hello.java
@@ -19,7 +19,7 @@
 //JAVA 21+
 //PREVIEW
 //DEPS dev.enola:enola:0.0.1-SNAPSHOT
-//REPOS mavencentral,jitpack
+//REPOS enola=https://docs.enola.dev/maven-repo/,mavencentral,jitpack
 
 import static java.lang.System.out;