Skip to main content

Requirements

Artifacts

Each is versioned and released together, so use the same version for all of them.

Choosing an engine

The SDK depends on ktor-client-core and bundles no HTTP engine. Engine choice is an application-level decision - connection pooling, TLS, proxy handling and HTTP/2 all live there - and a bundled engine would sit alongside whichever one the application already uses. Add exactly one:
…or pass an engine explicitly, which is also how you share the application’s own engine configuration:
If no engine is available, NexusClient.create raises NexusNoHttpEngineException, whose message names the exact dependency line to add.
A Ktor server dependency does not bring a Ktor client engine with it. Applications using the Ktor plugin still need one of the lines above.

GitLab package registry

The artifacts are hosted on the GitLab Maven Package Registry. It is public - no token is required to install.

Gradle (Kotlin DSL)

Gradle (Groovy DSL)

Maven

Transitive dependencies

What the SDK brings with it, and why. Four are api dependencies - their types appear in the SDK’s own signatures, so you can compile against them: No HTTP engine and no AWS SDK are declared - the engine is yours to pick, and the AWS SDK is needed only by the aws_iam WIF provider (see Workload identity). A CI job asserts both against the published POM on every pipeline.