Dependency Conflict Resolution

LLM4S transitively pulls several large dependencies. This page documents known conflicts and their resolutions.

Table of contents

  1. Which version does this apply to?
  2. Dependency footprint
  3. Conflict Matrix
  4. Logback conflict (0.4.x)
    1. Root cause
    2. Fix - Gradle (Kotlin DSL)
    3. Fix - Maven
    4. Fix - sbt
  5. Azure SDK transitive tree (0.4.x)
    1. Root cause
    2. Fix - Gradle (Kotlin DSL)
    3. Fix - Maven
  6. OkHttp and Kotlin standard library
    1. Root cause
    2. Fix - pin a version (Gradle, Kotlin DSL)
  7. Scala 3 artifact suffix in Gradle
    1. Root cause
    2. Fix
  8. Scala library version pinning
    1. Fix - Gradle (Kotlin DSL)
  9. Checking your dependency tree

Which version does this apply to?

In 0.5.0 LLM4S was split from one llm4s-core jar into focused modules (see the migration guide). The conflicts differ between the two shapes:

  • 0.4.x: llm4s-core contains everything, and declares logback-classic and com.azure:azure-ai-openai as compile dependencies.
  • 0.5.0 and later: llm4s-core and the provider modules depend on slf4j-api only (logback is test-scoped) and have no Azure dependency. Provider modules bring the vendor SDKs (openai-java, anthropic-java) and with them OkHttp and the Kotlin standard library.

These were checked against the 0.4.1 build definition and the dependency trees of the openai, anthropic and gemini modules on main.


Dependency footprint

What each artifact puts on the runtime classpath, measured with cs fetch against Maven Central. Each row is resolved together, as a project that declares those dependencies gets them:

Dependencies (llm4s 0.5.1) Jars Size (MB) Brings
llm4s-java-api 55 130.2 OkHttp, kotlin-stdlib, Jackson, Anthropic SDK, OpenAI SDK
llm4s-core 16 23.7 -
llm4s-core + llm4s-ollama 17 23.8 -
llm4s-core + llm4s-openai-compatible 17 24.2 -
llm4s-core + llm4s-gemini 17 24.0 -
llm4s-core + llm4s-anthropic 42 60.8 OkHttp, kotlin-stdlib, Jackson, Anthropic SDK
llm4s-core + llm4s-openai 42 95.2 OkHttp, kotlin-stdlib, Jackson, OpenAI SDK
llm4s-core + llm4s-agent + llm4s-ollama 22 30.1 -
  • llm4s-java-api 0.5.x brings every provider. It depends on llm4s-openai, llm4s-anthropic, llm4s-ollama, llm4s-gemini and llm4s-openai-compatible, so a Java user who calls only Ollama still gets both vendor SDKs: two and a half times the jars, and over four times the size, of core, the agent and one SDK-free provider. After 0.5.x the provider modules are optional dependencies of llm4s-java-api and llm4s-spring-boot-starter (#1496): the facade brings core and the agent, and you declare the provider modules you call, so llm4s-java-api with llm4s-ollama is the last row of the table. See the migration note.
  • Only two providers bring an SDK. Ollama, Gemini and the OpenAI-compatible providers add one small jar to core; OpenAI and Anthropic add their SDK and, with it, OkHttp, Jackson and the Kotlin standard library (see OkHttp and Kotlin standard library).

To measure a release, run scripts/dependency-footprint.sh [VERSION] (coursier’s cs on the PATH; the version defaults to the latest release). It prints this table.


Conflict Matrix

Conflict Affected scenario Symptom Resolution
logback-classic 1.4 vs 1.5 Spring Boot 3.2.x + llm4s-core 0.4.x Multiple SLF4J bindings warning or changed log format Exclude ch.qos.logback:logback-classic from llm4s; let Spring Boot manage it
Multiple SLF4J bindings Any project with 2+ logging frameworks SLF4J: Class path contains multiple SLF4J bindings Keep exactly one SLF4J implementation on the classpath
azure-ai-openai transitive tree Non-Azure projects on 0.4.x Extra Azure SDK jars on the classpath Exclude com.azure:azure-ai-openai from llm4s
OkHttp / Kotlin stdlib versions Ktor, Kotlin projects + the OpenAI or Anthropic modules Gradle upgrades OkHttp or kotlin-stdlib to the highest requested version Check with dependencyInsight; pin with a constraint if needed
Scala 3 micro-version mismatch Any multi-lib Gradle project IncompatibleClassChangeError at runtime Pin org.scala-lang:scala3-library_3 to 3.7.1 via resolutionStrategy
Scala _3 artifact suffix Gradle (does not auto-resolve) Could not resolve org.llm4s:llm4s-core Use explicit artifact names, e.g. llm4s-core_3

Logback conflict (0.4.x)

Root cause

llm4s-core 0.4.x declares ch.qos.logback:logback-classic as a compile dependency. Spring Boot 3.2.x uses 1.4.x via its BOM. Gradle’s default resolution strategy (highest wins) can pick the llm4s version, which may change log format output or trigger duplicate-binding errors if another binding is already present.

On main this no longer applies: the library modules depend on slf4j-api only.

Fix - Gradle (Kotlin DSL)

1
2
3
implementation("org.llm4s:llm4s-core_3:0.5.1") {
    exclude(group = "ch.qos.logback", module = "logback-classic")
}

Fix - Maven

1
2
3
4
5
6
7
8
9
10
11
<dependency>
    <groupId>org.llm4s</groupId>
    <artifactId>llm4s-core_3</artifactId>
    <version>0.5.1</version>
    <exclusions>
        <exclusion>
            <groupId>ch.qos.logback</groupId>
            <artifactId>logback-classic</artifactId>
        </exclusion>
    </exclusions>
</dependency>

Fix - sbt

1
libraryDependencies += ("org.llm4s" %% "llm4s-core" % "0.5.1").exclude("ch.qos.logback", "logback-classic")

Azure SDK transitive tree (0.4.x)

Root cause

llm4s-core 0.4.x includes the Azure OpenAI provider, which depends on com.azure:azure-ai-openai and, through it, the Azure core HTTP client stack. If you use neither Azure, this is dead weight and can conflict with a project’s own Netty version.

Fix - Gradle (Kotlin DSL)

1
2
3
implementation("org.llm4s:llm4s-core_3:0.5.1") {
    exclude(group = "com.azure", module = "azure-ai-openai")
}

Fix - Maven

1
2
3
4
5
6
<exclusions>
    <exclusion>
        <groupId>com.azure</groupId>
        <artifactId>azure-ai-openai</artifactId>
    </exclusion>
</exclusions>

OkHttp and Kotlin standard library

Root cause

openai-java and anthropic-java (pulled in by llm4s-openai and llm4s-anthropic) use OkHttp 4.12 and Kotlin standard library 1.9.x. Ktor and other Kotlin projects often bring their own versions of both. Gradle resolves to the highest version requested, which is normally harmless.

Do not exclude OkHttp from the SDKs: they need it at runtime.

Fix - pin a version (Gradle, Kotlin DSL)

1
2
3
4
5
dependencies {
    constraints {
        implementation("com.squareup.okhttp3:okhttp:4.12.0")
    }
}

Scala 3 artifact suffix in Gradle

Root cause

In sbt, %% automatically appends the Scala binary version suffix (_3). Gradle has no equivalent. If you write org.llm4s:llm4s-core:0.5.1 without a suffix, Gradle cannot resolve the artifact. LLM4S is Scala 3 only, so the suffix is always _3.

Fix

1
implementation("org.llm4s:llm4s-core_3:0.5.1")

Scala library version pinning

Multiple llm4s transitive dependencies may request different org.scala-lang:scala3-library_3 micro-versions. Gradle resolves to the highest, which is usually fine, but an explicit pin avoids unexpected upgrades.

Pin scala3-library_3 by name, not the whole org.scala-lang group. Scala 3 runs on the Scala 2.13 scala-library, which has no 3.x release, so a group-wide useVersion("3.7.1") fails to resolve with Could not find org.scala-lang:scala-library:3.7.1.

Fix - Gradle (Kotlin DSL)

1
2
3
4
5
6
7
configurations.all {
    resolutionStrategy.eachDependency {
        if (requested.group == "org.scala-lang" && requested.name == "scala3-library_3") {
            useVersion("3.7.1")
        }
    }
}

Checking your dependency tree

Run Gradle’s dependency insight to verify resolutions:

1
2
3
4
5
# Show what resolved logback-classic
./gradlew dependencies --configuration runtimeClasspath | grep logback

# Show full tree for a specific module
./gradlew dependencyInsight --dependency logback-classic --configuration runtimeClasspath

For sbt:

1
2
sbt "show dependencyTree"
sbt evicted