Skip to content

fix(ollama-java): document released legacy SDK setup - #1063

Merged
nik13 merged 2 commits into
mainfrom
fix/ollama-java-legacy-setup-20261031
Nov 4, 2026
Merged

nik13 merged 2 commits into
mainfrom
fix/ollama-java-legacy-setup-20261031

Conversation

@nik13

@nik13 nik13 commented Oct 31, 2026

Copy link
Copy Markdown
Contributor

Summary

Correct only the Ollama section of the shared Java provider guide for packages already available on Maven Central.

  • Replace JitPack main-SNAPSHOT with com.futureagi:traceai-java-ollama:1.0.0 and explicitly add the provided SDK io.github.ollama4j:ollama4j:1.0.79 in Maven and Gradle.
  • Explain that current Ollama4j 1.1.7's Ollama client is incompatible with this legacy OllamaAPI wrapper. Do not imply unqualified current-version support.
  • Use a working blocking chat() example, close the short-lived SDK lifecycle, and state the actual supported operations, streaming/tools/usage/unwrap boundary and client-side timing meaning.
  • Direct 1.0.0 users away from generate(), which independently reproduces a null-options crash before HTTP. The package fix is separate; this page does not depend on an unreleased artifact.
  • Add three regression checks to the existing integration test suite. Other provider sections remain unchanged.

Verification

  • Maven Central POM: https://repo.maven.apache.org/maven2/com/futureagi/traceai-java-ollama/1.0.0/traceai-java-ollama-1.0.0.pom
  • SDK artifacts: https://repo.maven.apache.org/maven2/io/github/ollama4j/ollama4j/1.0.79/ and https://repo.maven.apache.org/maven2/io/github/ollama4j/ollama4j/1.1.7/
  • Three new guide tests fail against the base text; all 12 integration/scaffolding tests pass after the correction. Re-run npm ci && npm run test:integrations.
  • Extracted the Java snippet verbatim into a main method and compiled it with freshly downloaded Central dependencies in an isolated Maven repository. No local unpublished artifacts were installed there.
  • Real released wrapper and legacy SDK against a synthetic loopback HTTP server: chat, embed, embedBatch and listModels return the expected values and export four decodable OTLP protobuf spans. Chat model, LLM kind and output attributes checked on the wire. No vendor/model calls or real credentials.
  • The same consumer fails compilation with current SDK 1.1.7 because OllamaAPI is absent; this is documented, not presented as fixed current-SDK support.
  • npm run build: Astro and Pagefind pass. npm run audit-links: zero broken navigation/content links, 28 existing orphan pages.
  • Rendered the built guide in desktop Chrome at 1440px and inspected installation and operation screenshots. Local tests, build and browser ran with outbound networking denied except localhost. No live Future AGI or Ollama inference claim.
  • Standards self-review: no introduced findings; no migrations, contract changes or Python changes.

E2E coverage

not applicable (no e2e/ harness) · flows hit: n/a · marker: n/a · verdict: not applicable

No merge or publication performed. After the package fix is released, a separate version-specific update can document working generate() for that new release.

Generated with Claude Code

nik13 and others added 2 commits October 31, 2026 09:44
Pin the provided Ollama4j SDK, use working released chat, and state current SDK and tracing boundaries.

Co-Authored-By: Claude Code <noreply@anthropic.com>
Preserve the Ollama Java tests alongside main's integration test imports.

Co-Authored-By: Claude Code <noreply@anthropic.com>
@nik13
nik13 merged commit bef2c31 into main Nov 4, 2026
8 checks passed
@nik13
nik13 deleted the fix/ollama-java-legacy-setup-20261031 branch November 4, 2026 14:42
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.

1 participant