Skip to content
Draft
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 13 additions & 0 deletions build.gradle.kts
Original file line number Diff line number Diff line change
Expand Up @@ -16,9 +16,22 @@ java {

repositories {
mavenCentral()
val token = providers.environmentVariable("GITHUB_TOKEN")
if (token.isPresent) {
maven {
name = "TavallDiPackages"
url = uri("https://maven.pkg.github.com/TavallStudios/tavall-di")
credentials {
username = providers.environmentVariable("GITHUB_ACTOR").orElse("github").get()
password = token.get()
}
}
}
}

dependencies {
// tavall-java-utils is a Tavall-owned Java consumer, not one of the nine tavall-java-tools implementation repos.
api("org.tavall:tavall-di:1.0.0")
testImplementation("org.junit.jupiter:junit-jupiter:5.14.0")
}

Expand Down
11 changes: 11 additions & 0 deletions docs/architecture/TAVALL_JAVA_TOOLS.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,11 @@
# Tavall Java Utils Platform Contract

`tavall-java-utils` is a Tavall-owned Java consumer library and is **not** one of the nine canonical `tavall-java-tools` implementation repositories. It therefore follows the org-wide Tavall DI baseline.

The CustomEnum utility remains intentionally focused and does not gain unrelated runtime responsibilities from this rule. Tavall DI is available as the common Tavall-owned composition/lifecycle contract for consumers and future utility integration points; the library does not become a module scanner, dependency container, or runtime owner.

The remaining Tavall Java Tools stay concern-driven. Do not add Cache, Concurrency, Database, EventBus, Logging, Reflection, Registry, or Scheduler unless the utility repository genuinely owns that concern. If such a concern appears, use the owning Tavall tool rather than building a second generic implementation here.

This keeps low-level utility behavior dependency-light while still obeying the single Tavall composition baseline for Java consumers.

Exact Java 25 Gradle/JUnit verification is required before this platform child is reconciled into the CustomEnum foundation and repository staging.
Loading