pluginManagement { repositories { google { content { includeGroupByRegex("com\\.android.*") includeGroupByRegex("com\\.google.*") includeGroupByRegex("androidx.*") } } mavenCentral() gradlePluginPortal() } } dependencyResolutionManagement { repositoriesMode.set(RepositoriesMode.FAIL_ON_PROJECT_REPOS) repositories { google() mavenCentral() } } rootProject.name = "incido" include(":app") include(":composeApp") include(":core:domain") include(":core:data") // Phase 1 (M1a): the desktop build of the same data layer. It compiles // :core:data's platform-neutral sources against the JVM ObjectBox runtime — // see core/data-jvm/build.gradle.kts for why this is a sibling module and not // a multiplatform one. include(":core:data-jvm") // Phase 1 (M1b): the desktop application — a Compose Multiplatform window over // :core:data-jvm. Owns its own library (XDG data dir); the encrypted backup // file is the only bridge to the phone (M2). include(":desktopApp") // Phase 1 (M2 task 1): the backup bridge — codecs + stream-based // import/export, extracted from :composeApp so :desktopApp can read and // write the SAME file format the phone produces. Plain kotlin("jvm"), // consumed by both platforms. include(":core:backup") // Phase 1 (M3 task 1): user settings, same extraction logic as :core:backup. // SettingsRepository now takes an injected DataStore; Android // supplies the Context-extension store, the desktop build a file-based one — // both producing the same `.preferences_pb` format, same keys. include(":core:settings") // --- (Phase 1, M4.5) The Phase-0 spike modules :spike:data-jvm and // :spike:compose-jvm are GONE (§6.6): everything they proved now lives in // :core:data-jvm, :composeApp (jvm target) and :desktopApp, and the real // screens have been hosted since M4.5b — the spike's reason to exist // expired. Its findings live on in tools/DESKTOP_FEASIBILITY.md.