Repository navigation
feat(java): prepare Maven Central releases and retain JitPack - #302
Merged
Merged
Conversation
Use com.futureagi coordinates, add a BOM and release-only Central publishing profile, and verify all Java modules and release artifacts in CI. Keep package imports unchanged and document commit-pinned JitPack installs. Co-Authored-By: Claude Code <noreply@anthropic.com>
7 tasks
nik13
added a commit
that referenced
this pull request
Oct 29, 2026
Align the deployment environment with the actual release profile in #302; no local GnuPG keyring is needed. Co-Authored-By: Claude Code <noreply@anthropic.com>
Flatten only JitPack consumer POMs, preserve Central coordinates, remove inherited test scopes from public dependency management, and compile external README, Spring Boot, and BOM consumers in CI. Co-Authored-By: Claude Code <noreply@anthropic.com>
The first clean public consumer exposed that JitPack remaps direct dependencies but leaves dependencyManagement at Central coordinates. Prepare only installed flattened POMs for harvesting and regress both managed mapping and rejection of normal Central POMs. Co-Authored-By: Claude Code <noreply@anthropic.com>
Use the checksum-verified Maven 3.9.9 wrapper, chain the harvesting step to successful installation, and keep the small preparation script compatible with Python 3.5 on JitPack legacy images. Co-Authored-By: Claude Code <noreply@anthropic.com>
Prefer shasum when available because the macOS sha256sum check mode does not accept the GNU stdin syntax. Keep SHA-256 verification mandatory on both paths. Co-Authored-By: Claude Code <noreply@anthropic.com>
This was referenced Oct 29, 2026
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
Prepare the existing Java SDK for Maven Central releases under
com.futureagi, with JitPack retained for commit-pinned, unreleased builds. This PR targets dev; it does not merge, tag, or publish a Central release.ai.traceai.*Java package/import unchanged.traceai-bomcovering all 24 SDK modules. The parent POM remains the SDK version source (1.0.0), including the runtime version resource.central-publishing-maven-plugin(central,autoPublish=true,waitUntil=published).FI_*authentication variables, and the module-derived integration list.Independent-verifier fixes
All three blocking findings are fixed in follow-up commits on this same branch.
P1: JitPack builds must produce installable artifacts, not merely report
okJitPack could publish a successful build while child POMs referred to an unavailable
traceai-java-parent. The opt-injitpackprofile now installs self-contained, flattened POMs without parent references. A JitPack-only post-install hook explicitly maps internal dependencies and BOM dependency management to the exact requested JitPack coordinates; JitPack's own remapping did not handle managed dependencies. Normal and Central release POMs retaincom.futureagiand their original parent structure.JitPack now uses a checksum-verified Maven 3.9.9 wrapper, avoiding image-dependent Maven versions. The harvesting hook supports the legacy image's Python 3.5 syntax and runs only after a successful Maven installation.
Current head
f5e5b9045295949416d66e6117cd44b7035520a6is verified end to end:ok, all 26 modules.com.futureagiartifacts. Public BOM/OpenAI/core/starter/Spring-AI POMs have no parent references, and the public BOM manages all 24 SDK modules at the exact JitPack group and head SHA.Reproduce from the repository root, with JDK 21 and Maven available:
P2: Spring Boot instructions must retain direct OpenAI instrumentation
Both Maven and Gradle instructions now describe the starter as additional, not a replacement for
traceai-java-openai. The README's actual Java snippet compiles with both dependencies in an independent Maven application and with the corrected Gradle dependency block. A negative control using only the starter fails withpackage ai.traceai.openai does not exist, as expected.P2: Public BOM must not force consumer dependencies into test scope
The parent manages test-library versions only; the reactor's actual dependencies already declare
scope=testindividually. The public BOM no longer forces OpenTelemetry SDK testing, JUnit, AssertJ, or Mockito into test scope.An independent application imports the BOM and uses all five managed artifacts in
src/main/java, without versions or explicit scope overrides. It compiles with both normal Central-coordinate POMs and public current-head JitPack POMs. The same fixture fails with the previous parent POM's scopes and succeeds after replacing only that parent POM with the fix. Gradle's main-classpath consumer also compiles.Validation
Heavy local builds ran through the shared build lock, with JDK 21. The final wrapper-based checks use Maven 3.9.9.
./mvnw -B -ntp verify: 26 reactor projects successful, 14 tests passed, 109 credential-gated provider E2E tests skipped, no failures/errors../mvnw -B -ntp -P release -Dgpg.skip package: successful; all 24 binary/source/Javadoc JAR sets built, with Javadoc errors still fatal.actionlint; shell syntax and a fresh-cache wrapper download/checksum validation pass locally.1883f49e-4920-44c1-2dc6-5fad601956ce, one OK LLM span, modelgpt-6.1-sol, tokens 314 / 11 / 325, input/output present. No provider calls were needed for this fix round.Maintainer prerequisites and limits
com.futureagiin the Sonatype Central Portal and configure servercentralwithMAVEN_CENTRAL_USERNAME/MAVEN_CENTRAL_PASSWORD, plusMAVEN_GPG_PRIVATE_KEY/MAVEN_GPG_PASSPHRASE.mvn -B -ntp -P release deployis a real publish operation, not a dry run. It was not executed. Production signing and a Central upload remain intentionally untested.Interaction with #204
The separate Spring AI 1.1 compatibility PR #204 overlaps the Java POMs/examples and README. The original read-only merge simulation confirmed a README conflict. When combining these PRs, preserve
com.futureagi, the release profile/BOM, and the JitPack-specific preparation, and migrate #204's new compatibility-cell POM coordinates too. This PR deliberately retains the current1.0.0-M4Spring AI dependency; its implementation/test changes are not copied here.🤖 Generated with Claude Code