Parent
#65
What to build
Regroup the existing reactive modules physically into reactive/datasource/*, so both SDK families
will sit side by side under reactive/ once StreamLink is imported. Move physical folders only —
keep every Gradle project path unchanged by giving each module a projectDir override in
settings.gradle.kts, so published coordinates stay pinned and no cross-module project(":reactive:…")
reference changes. The five modules (reactive/core, api, kotlin, java-flow, reactivestreams)
move under reactive/datasource/; their .api snapshot files move with them.
This is a pure structural prefactor: nothing about the public API or behaviour changes.
Acceptance criteria
Blocked by
- None - can start immediately
Parent
#65
What to build
Regroup the existing reactive modules physically into
reactive/datasource/*, so both SDK familieswill sit side by side under
reactive/once StreamLink is imported. Move physical folders only —keep every Gradle project path unchanged by giving each module a
projectDiroverride insettings.gradle.kts, so published coordinates stay pinned and no cross-moduleproject(":reactive:…")reference changes. The five modules (
reactive/core,api,kotlin,java-flow,reactivestreams)move under
reactive/datasource/; their.apisnapshot files move with them.This is a pure structural prefactor: nothing about the public API or behaviour changes.
Acceptance criteria
reactive/datasource/on disk.datasourcex-kotlin,datasourcex-reactive-core, etc.)../gradlew checkpasses andapiCheckreports no.apidiff..apisnapshot files sit alongside their relocated modules..github/workflows/build.yml) point at the newreactive/datasource/<variant>locations.Blocked by