Rename langchain4j module to llama-langchain4j; wire CI build/test + Central publish

Cleans up the integration of the merged langchain4j adapters (PR #284) so the
module is built, gated, version-locked and releasable — without touching the
native build/release pipeline.

- Rename artifact + directory langchain4j-jllama -> llama-langchain4j so it
  groups with the core net.ladenthin:llama family (Java package unchanged).
- Pin the core dependency to ${project.version} (drops the drift-prone
  jllama.version property); a CI guard fails the build if the module version
  ever diverges from the core version (standalone module can't inherit it from
  a reactor).
- Add per-artifact release plumbing (sources + javadoc + gpg + Central
  Publishing) mirroring the core release profile, so the module can deploy to
  Maven Central at the same version.
- publish.yml: new test-java-llama-langchain4j job (install core Java jar,
  version-lockstep guard, mvn verify — builds the javadoc jar so a release-time
  javadoc break is caught in PR CI). publish-snapshot/publish-release now
  depend on it and deploy the module alongside the core.
- REUSE.toml + README updated to the new name; CLAUDE.md documents the module,
  why it is a separate artifact (not a classifier), and the CI/publish wiring.

Verified locally: core Java jar installs, module builds green (7 mapping tests
pass, 2 model-backed integration tests self-skip), and the main/sources/javadoc
jars all build under doclint=all.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Rt1paYztGJ2AKUuBuAGDXE

Author: claude

.github/workflows/publish.yml

@@ -93,6 +93,45 @@ jobs:
           echo "=== internal package dependency graph (jdeps, bytecode) ==="
           jdeps -verbose:package target/classes | grep 'net.ladenthin.llama' || true
 
+  # ---------------------------------------------------------------------------
+  # Sibling module `llama-langchain4j` (LangChain4j adapters). Pure Java, no native
+  # code and no per-classifier matrix: it compiles against the core's stable Java API
+  # (identical across every classifier) and the backend is a runtime choice for the
+  # consumer. This job installs the core Java jar, guards that the module version is in
+  # lockstep with the core, then builds + tests the module (Java 17; langchain4j 1.x
+  # baseline). It runs its mapping unit tests; the model-backed integration test
+  # self-skips without a GGUF. `verify` also builds the javadoc/sources jars so a
+  # release-time javadoc break is caught here in PR CI.
+  # ---------------------------------------------------------------------------
+
+  test-java-llama-langchain4j:
+    name: Build and Test llama-langchain4j
+    needs: startgate
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v7
+      - uses: actions/setup-java@v5
+        with:
+          java-version: ${{ env.JAVA_VERSION }}
+          distribution: temurin
+      - name: Version lockstep guard (module version must equal core version)
+        shell: bash
+        run: |
+          CORE=$(mvn -q -DforceStdout help:evaluate -Dexpression=project.version | tail -n1)
+          MOD=$(mvn -q -DforceStdout -f llama-langchain4j/pom.xml help:evaluate -Dexpression=project.version | tail -n1)
+          echo "core=$CORE module=$MOD"
+          if [ "$CORE" != "$MOD" ]; then
+            echo "::error::Version drift: core ($CORE) != llama-langchain4j ($MOD). Keep llama-langchain4j/pom.xml <version> in lockstep with the root pom.xml."
+            exit 1
+          fi
+      - name: Install core net.ladenthin:llama jar (Java only)
+        run: >
+          mvn -B --no-transfer-progress -DskipTests -Denforcer.skip=true
+          -Dspotless.check.skip=true -Dspotbugs.skip=true
+          -Dmaven.javadoc.skip=true -Dmaven.source.skip=true -Dgpg.skip=true install
+      - name: Build and test llama-langchain4j
+        run: mvn -B --no-transfer-progress -f llama-langchain4j/pom.xml verify
+
   # ---------------------------------------------------------------------------
   # Build the llama.cpp WebUI ONCE, from the same pinned tag CMakeLists.txt fetches,
   # and share it to every native build as the generated, platform-independent
@@ -1665,7 +1704,7 @@ jobs:
 
   publish-snapshot:
     name: Publish Snapshot to Central
-    needs: [check-snapshot, crosscompile-linux-x86_64-cuda, crosscompile-android-aarch64-opencl, code-style]
+    needs: [check-snapshot, crosscompile-linux-x86_64-cuda, crosscompile-android-aarch64-opencl, code-style, test-java-llama-langchain4j]
     if: needs.check-snapshot.result == 'success' && inputs.publish_to_central
     runs-on: ubuntu-latest
     environment: maven-central
@@ -1731,11 +1770,23 @@ jobs:
           MAVEN_USERNAME: ${{ secrets.CENTRAL_USERNAME }}
           MAVEN_PASSWORD: ${{ secrets.CENTRAL_TOKEN }}
           MAVEN_GPG_PASSPHRASE: ${{ secrets.GPG_PASSPHRASE }}
+      # Deploy the sibling llama-langchain4j at the same version. The core `deploy`
+      # above ran through `install`, so net.ladenthin:llama is in the local repo for
+      # the module to resolve. Standalone module (not in the reactor), so it is a
+      # separate deploy invocation.
+      - name: Publish snapshot (llama-langchain4j)
+        run: mvn --batch-mode --no-transfer-progress -f llama-langchain4j/pom.xml -P release -Dmaven.test.skip=true deploy
+        env:
+          MAVEN_USERNAME: ${{ secrets.CENTRAL_USERNAME }}
+          MAVEN_PASSWORD: ${{ secrets.CENTRAL_TOKEN }}
+          MAVEN_GPG_PASSPHRASE: ${{ secrets.GPG_PASSPHRASE }}
       - name: Collect signed artifacts
         run: |
           mkdir -p signed-snapshot-assets
           cp target/*.jar signed-snapshot-assets/ 2>/dev/null || true
           cp target/*.jar.asc signed-snapshot-assets/ 2>/dev/null || true
+          cp llama-langchain4j/target/*.jar signed-snapshot-assets/ 2>/dev/null || true
+          cp llama-langchain4j/target/*.jar.asc signed-snapshot-assets/ 2>/dev/null || true
       - uses: actions/upload-artifact@v7
         with:
           name: signed-snapshot-assets
@@ -1770,7 +1821,7 @@ jobs:
   publish-release:
     name: Publish Release to Central
     if: needs.check-tag.result == 'success' && inputs.publish_to_central
-    needs: [check-tag, crosscompile-linux-x86_64-cuda, crosscompile-android-aarch64-opencl, code-style]
+    needs: [check-tag, crosscompile-linux-x86_64-cuda, crosscompile-android-aarch64-opencl, code-style, test-java-llama-langchain4j]
     runs-on: ubuntu-latest
     environment: maven-central
     permissions:
@@ -1826,11 +1877,23 @@ jobs:
           MAVEN_USERNAME: ${{ secrets.CENTRAL_USERNAME }}
           MAVEN_PASSWORD: ${{ secrets.CENTRAL_TOKEN }}
           MAVEN_GPG_PASSPHRASE: ${{ secrets.GPG_PASSPHRASE }}
+      # Deploy the sibling llama-langchain4j at the same version. The core `deploy`
+      # above ran through `install`, so net.ladenthin:llama is in the local repo for
+      # the module to resolve. Standalone module (not in the reactor), so it is a
+      # separate deploy invocation.
+      - name: Publish release (llama-langchain4j)
+        run: mvn --batch-mode --no-transfer-progress -f llama-langchain4j/pom.xml -P release -Dmaven.test.skip=true deploy
+        env:
+          MAVEN_USERNAME: ${{ secrets.CENTRAL_USERNAME }}
+          MAVEN_PASSWORD: ${{ secrets.CENTRAL_TOKEN }}
+          MAVEN_GPG_PASSPHRASE: ${{ secrets.GPG_PASSPHRASE }}
       - name: Collect signed artifacts
         run: |
           mkdir -p signed-release-assets
           cp target/*.jar signed-release-assets/ 2>/dev/null || true
           cp target/*.jar.asc signed-release-assets/ 2>/dev/null || true
+          cp llama-langchain4j/target/*.jar signed-release-assets/ 2>/dev/null || true
+          cp llama-langchain4j/target/*.jar.asc signed-release-assets/ 2>/dev/null || true
       - uses: actions/upload-artifact@v7
         with:
           name: signed-release-assets

CLAUDE.md

@@ -1219,6 +1219,48 @@ keeping it clear of the JPMS module-mode javadoc trap that bit BAF. **Before rai
 javadoc source level to ≥ 9, read**
 [`../workspace/policies/jpms-module-descriptor.md`](../workspace/policies/jpms-module-descriptor.md).
 
+## LangChain4j integration (`llama-langchain4j` sibling module)
+
+`llama-langchain4j/` adapts a `LlamaModel` to LangChain4j's `ChatModel`,
+`StreamingChatModel`, `EmbeddingModel` and `ScoringModel` interfaces **in-process over
+JNI** (no HTTP hop). It is a **standalone sibling module**, deliberately *not* in the root
+reactor, so the native build/release pipeline is untouched.
+
+Why it is a **separate artifact** and not a classifier of the core: langchain4j 1.x
+requires **Java 17** (the core stays Java 8), and classifiers share the core's single POM —
+adding `langchain4j-core` there would force it (and the Java 17 floor) on every plain
+`net.ladenthin:llama` consumer. A separate `artifactId` with its own POM is the only way to
+keep that dependency (and Java floor) off the core. It is pure Java with **no per-classifier
+matrix**: it compiles against the core's Java API, which is identical across every native
+classifier; the backend (CPU/CUDA/OpenCL/Vulkan) is a runtime classpath choice for the
+consumer.
+
+Wiring:
+
+1. **`llama-langchain4j/pom.xml`** — `net.ladenthin:llama-langchain4j`, `release 17`,
+   depends on `net.ladenthin:llama:${project.version}` (so the core dep always matches the
+   module's own version) and `dev.langchain4j:langchain4j-core`. Carries its own
+   sources/javadoc/gpg + `release` profile (Central requires per-artifact signing; the module
+   has no parent to inherit them from — plugin versions are pinned in lockstep with the root
+   `pom.xml`). Java package stays `net.ladenthin.llama.langchain4j` (package name need not track
+   the artifactId).
+2. **`.github/workflows/publish.yml`** — the `test-java-llama-langchain4j` job installs the
+   core Java jar, runs a **version-lockstep guard** (module version must equal core version,
+   else the build fails — the standalone module can't inherit `${project.version}` from a
+   reactor), then `mvn -f llama-langchain4j/pom.xml verify` (mapping unit tests run; the
+   model-backed `JllamaChatModelIntegrationTest` self-skips without a GGUF; `verify` also
+   builds the javadoc jar so a release-time javadoc break is caught in PR CI). The
+   `publish-snapshot`/`publish-release` jobs `needs:` this job and, after the core `deploy`
+   (which installs the core jar locally), run a second `deploy` of the module at the same
+   version.
+3. **Version bumps** — when the root `pom.xml` `<version>` changes, bump
+   `llama-langchain4j/pom.xml` `<version>` to match in the same commit, or the lockstep guard
+   reds CI.
+
+**Open follow-ups** (documented in `llama-langchain4j/README.md`): tool calling
+(`ToolSpecification` ↔ jllama `ToolDefinition`), `response_format`/JSON mode, and multimodal
+user input (currently flattened to text).
+
 ## Open TODOs
 
 Open TODOs for this repo live in [`TODO.md`](TODO.md). Cross-repo status

REUSE.toml

@@ -24,7 +24,7 @@ path = [
     ".github/ISSUE_TEMPLATE/bug_report.md",
     ".github/ISSUE_TEMPLATE/feature_request.md",
     ".claude/commands/find-cpp-duplication.md",
-    "langchain4j-jllama/README.md",
+    "llama-langchain4j/README.md",
 ]
 SPDX-FileCopyrightText = [
     "2023-2025 Konstantin Herud",

langchain4j-jllama/pom.xml

@@ -1,4 +1,4 @@
-# langchain4j-jllama
+# llama-langchain4j
 
 [LangChain4j](https://github.com/langchain4j/langchain4j) adapters backed by an **in-process**
 [java-llama.cpp](https://github.com/bernardladenthin/java-llama.cpp) model over JNI — no HTTP server,
@@ -61,7 +61,7 @@ ScoringModel reranker     = new JllamaScoringModel(rerankLlama);
 ```xml
 <dependency>
     <groupId>net.ladenthin</groupId>
-    <artifactId>langchain4j-jllama</artifactId>
+    <artifactId>llama-langchain4j</artifactId>
     <version>5.0.4-SNAPSHOT</version>
 </dependency>
 ```
@@ -79,7 +79,7 @@ build here:
 mvn -DskipTests install
 
 # then build/test this module
-cd langchain4j-jllama
+cd llama-langchain4j
 mvn test
 ```