Skip to content

Support running from composite build root (includeBuild) #5

@Nek-12

Description

@Nek-12

Problem

Running ksrc from a composite build root (uses includeBuild) resolves only the root project and does not traverse included builds. This makes ksrc search return no sources even though the included build has the dependencies.

Repro

In an app monorepo, root includes an app via includeBuild("apps/app1").

ksrc search "pro.respawn.flowmvi:*" -q "fun.*updateState"

Actual

E_NO_SOURCES: no sources resolved.

Expected

From composite root, resolve across included builds by default (or at least provide a clear error + guidance). The spec currently says multi-project builds resolve all subprojects by default; composite builds are not covered and should probably follow the same spirit.

Workaround

Run from the included build root instead:

cd ../apps/app1
ksrc search "pro.respawn.flowmvi:*" -q "fun.*updateState"

Notes

  • Root settings.gradle.kts uses includeBuild("apps/app1").
  • ksrc currently uses a Gradle init script that walks root.allprojects, which does not include included builds.
  • The recent fix for Gradle exclusive-lock errors moved resolution into per-project tasks; any composite build support should avoid reintroducing the lock issue.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions