Repository navigation
fix(ollama-java): document released legacy SDK setup - #1063
Merged
Merged
Conversation
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>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Correct only the Ollama section of the shared Java provider guide for packages already available on Maven Central.
main-SNAPSHOTwithcom.futureagi:traceai-java-ollama:1.0.0and explicitly add the provided SDKio.github.ollama4j:ollama4j:1.0.79in Maven and Gradle.Ollamaclient is incompatible with this legacyOllamaAPIwrapper. Do not imply unqualified current-version support.chat()example, close the short-lived SDK lifecycle, and state the actual supported operations, streaming/tools/usage/unwrap boundary and client-side timing meaning.generate(), which independently reproduces a null-options crash before HTTP. The package fix is separate; this page does not depend on an unreleased artifact.Verification
npm ci && npm run test:integrations.npm run build: Astro and Pagefind pass.npm run audit-links: zero broken navigation/content links, 28 existing orphan pages.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