Shared Kotlin Multiplatform libraries for Coderwise apps, published to Maven Central under the com.coderwise.libs group. Consumers need only mavenCentral() — no credentials.

All modules target Android · iOS (arm64, sim-arm64) · JS · Desktop (the map modules additionally target Wasm/JS) and publish under com.coderwise.libs. "Latest" is the newest version on Maven Central; modules without one are consumed via mavenLocal until first released.

The sample/ directory holds an unpublished demo app for the map libraries that runs on all five platforms (Android, iOS, Desktop, JS, Wasm/JS) — see its README for run commands.

Each module is versioned and released independently, via the vanniktech maven-publish plugin (Central Portal upload, GPG signing, sources/javadoc jars).

The release tag is the single source of truth for the version. Tag a module release as <module>-v<version>; the publish workflow parses it, passes -PlibVersion, and publishes only that module:

git tag utils-v0.4.0    && git push origin utils-v0.4.0     # → com.coderwise.libs:utils:0.4.0
git tag map-core-v0.1.6 && git push origin map-core-v0.1.6  # → com.coderwise.libs:map-core:0.1.6

Note: the publish workflow runs on a macOS runner (required for the iOS Kotlin/Native targets), which bills GitHub Actions minutes at 10×. Validate locally with publishToMavenLocal first; publish deliberately.

The same workflow also accepts a manual workflow_dispatch (module + version inputs). It needs these repo secrets (same values as the other coderwise repos — com.coderwise namespace is already verified): MAVEN_CENTRAL_USERNAME, MAVEN_CENTRAL_PASSWORD, SIGNING_KEY_ID, SIGNING_PASSWORD, GPG_KEY_CONTENTS.

Local, keyless (publishes as 0.0.0-LOCAL unless -PlibVersion is given):

./gradlew :utils:publishToMavenLocal

Drop it in as a top-level folder with a build.gradle.kts (settings.gradle.kts auto-includes it). Mirror :utils: apply the vanniktech plugin, read the version from libVersion (default 0.0.0-LOCAL), set coordinates("com.coderwise.libs", "<name>", …). Release it with a <name>-v<version> tag — no workflow changes needed.

:utils originated in coderwise/maps-mobile (published through 0.2.0) and was extracted here; com.coderwise.libs:utils coordinates are unchanged, so consumers required no edits beyond the version bump. The :database, :settings, :location, :permissions, :map-core, and :map-engine modules were added here to share infrastructure across the *.mobile apps.