Skip to main content

Java Compatibility Evidence — July 2026

This archive records whether the Java combination generated in July 2026 was ready to build and run. Its blockers are not current status. Use Latest Versions for current coordinates and Cross-language Conformance Status for current committed capability evidence.

Archived Observed Combination​

LayerObserved valueEvidenceCurrent conclusion
Generator Server20260710.110004Official endpoint and live generationGeneration baseline for this archived campaign.
Maven client1.1.1Plugin source/help and live dynamic target catalogeval, dynamic generate, and list-services verified.
Targetjava-lib-coreLive generationGeneration succeeds with a concrete model version.
Runtime1.525-RELEASEGenerated POM and official artifacts/sourceRuntime baseline for this archived campaign.
Java21Generated compiler release propertyObserved target level, not a universal minimum.
Spring Boot BOM4.1.0Generated POMEmitted dependency-management value; application integration not executed.
SQLite artifactio.teaql:teaql-sqlite:1.525-RELEASEPublished TeaQL Maven artifactPublished coordinate differs from the generated POM.

Archived Build Decision​

The generated combination was not executable in that campaign. Two independent generator/runtime mismatches were recorded:

  1. The generated POM requests nonexistent io.teaql:teaql-data-service-sqlite:1.525-RELEASE instead of the published io.teaql:teaql-sqlite:1.525-RELEASE.
  2. After using the published artifact in an independent diagnostic build, generated entities use internalSet/internalGet, while teaql-core 1.525-RELEASE exposes __internalSet/__internalGet.

java-app-console also failed generation because the live server template was missing application.properties.stg. Preserve these reports and fix the generator templates; do not patch committed generated source.

Upgrade or Adoption Check​

For every Java target/runtime change:

  1. Query the live target catalog with Maven plugin help pinned to the selected version.
  2. Evaluate an unchanged model with a concrete root version.
  3. Generate into a clean directory.
  4. Record the generated Java level, framework BOM, TeaQL artifacts, and provider coordinate.
  5. Resolve dependencies only from documented repositories.
  6. Compile without editing generated files.
  7. Execute one query with non-empty comment and purpose before the terminal, and one auditAs mutation.
  8. Regenerate after a one-field model change and review the API/metadata diff.
  9. Record the exact JDK, database/driver, command output, and rollback input.

Until steps 6–8 pass, describe the combination as generated or blocked—not tested or supported.

Framework Boundary​

The target catalog observed in that campaign advertised Spring Boot, Quarkus, and Micronaut targets. Catalog presence proved discovery only. That campaign did not produce clean framework build/runtime evidence. Framework datasource, lifecycle, serialization, transaction, native-image, and deployment claims require their own generated build.

Related pages: