Skip to content

Release 5.0.4: LangChain4j integration, fine-tuning API, and Maven reactor#291

Merged
bernardladenthin merged 2 commits into
mainfrom
claude/java-llama-cpp-release-vaesh7
Jul 2, 2026
Merged

Release 5.0.4: LangChain4j integration, fine-tuning API, and Maven reactor#291
bernardladenthin merged 2 commits into
mainfrom
claude/java-llama-cpp-release-vaesh7

Conversation

@bernardladenthin

Copy link
Copy Markdown
Owner

Summary

  • Release 5.0.4 with LangChain4j in-process adapters (ChatModel, StreamingChatModel, EmbeddingModel, ScoringModel), experimental fine-tuning API (LlamaTrainer), and model introspection (ModelMeta).
  • Restructured build into a Maven reactor: native JNI core moved to llama/ module under new aggregator parent POM (llama-parent), alongside new llama-langchain4j module. Both inherit a single version and ship in lockstep. Published coordinates (net.ladenthin:llama) unchanged.
  • Upgraded llama.cpp from b9842 to b9859; all four local patches apply unchanged.
  • Updated version in all three POMs (root, llama/, llama-langchain4j/) and documentation (README, CHANGELOG).

Test plan

  • CI is green on this branch
  • Docs / CHANGELOG updated (CHANGELOG.md with 5.0.4 entry, README.md version bumps, CLAUDE.md clarified version-bump procedure)

Related issues / PRs

Closes the 5.0.4 release.

Checklist

  • I have read CONTRIBUTING.md and CODE_OF_CONDUCT.md
  • My commits follow Conventional Commits
  • No security-sensitive changes

https://claude.ai/code/session_01QEgh6vtcPWAgQ6scK8pJk7

claude added 2 commits July 2, 2026 11:52
Bump the reactor (llama-parent + llama + llama-langchain4j) from
5.0.4-SNAPSHOT to 5.0.4, point the README release dependency examples at
5.0.4 (snapshot examples stay 5.0.4-SNAPSHOT), and write the CHANGELOG
[5.0.4] section (LangChain4j adapters, LlamaTrainer fine-tuning API,
ModelMeta introspection, Maven reactor restructure, llama.cpp b9842->b9859).

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01QEgh6vtcPWAgQ6scK8pJk7
The "change the root pom.xml <version> only" note was aspirational and
never exercised (the only prior bump predated the llama/ reactor split).
In reality each child hardcodes the parent version in its <parent><version>
pointer and there is no ${revision}/CI-friendly setup, so a version change
must touch all three poms in lockstep or the reactor build fails with
"Could not find artifact net.ladenthin:llama-parent:pom:X.Y.Z". Document the
three edit sites, recommend `mvn versions:set`, and note that ${revision} +
flatten-maven-plugin would be needed for true root-only bumps.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01QEgh6vtcPWAgQ6scK8pJk7
@bernardladenthin bernardladenthin merged commit 6fb5347 into main Jul 2, 2026
10 of 48 checks passed
@bernardladenthin bernardladenthin deleted the claude/java-llama-cpp-release-vaesh7 branch July 2, 2026 12:08
@claude

claude Bot commented Jul 2, 2026

Copy link
Copy Markdown

Review of PR #291 - Release 5.0.4

Version bumps: All three POMs correctly synchronized to 5.0.4 (root + two children).

README: All 10 version references updated (5.0.3 → 5.0.4). Snapshot example uses 5.0.4-SNAPSHOT.

CHANGELOG: Well-structured with Added/Changed sections. Date correct (2026-07-02). Tracks llama.cpp b9842→b9859.

CLAUDE.md: Second commit fixes aspiration to reality—now documents that all three POMs must be bumped in lockstep, provides mvn versions:set remedy, explains the failure mode clearly.

Commits: Both follow Conventional Commits. Clear messages. Co-Authored properly.

Scope: Surgical diff (POMs, README, CHANGELOG, CLAUDE.md only).

Status: No issues found. Approved for merge.

@sonarqubecloud

sonarqubecloud Bot commented Jul 2, 2026

Copy link
Copy Markdown

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants