feat(plugins): read the Maven / Gradle dependency graph (API 1.10) (#3829)

Plugins had to run mvn dependency:tree / gradlew dependencies themselves or parse build files. A new build interface in wit/workspace.wit, build.dependencies(project, module), returns the graph the Dependency Analyzer has as a flat list of dependency-node records (group, artifact, version, scope, status, requested version, parent), each module a root, behind the low-risk build.read capability in trusted projects. Nothing is resolved by the call: Maven returns the trees cached by the last Reload (declared dependencies before one); Gradle dependency reports, which only lived in the frontend, are now saved per project and configuration in the build cache and dropped on a build-file change. Capped at 100,000 nodes per call. SDK: Project::build_dependencies with a mock; checked-in components rebuilt.

Closes #3715

Co-authored-by: bertyhell <1710840+bertyhell@users.noreply.github.com>
This commit is contained in:
Bert Verhelst
2026-11-17 03:29:39 +08:00
committed by GitHub
co-authored by bertyhell
parent 2b69d64055
commit e6daffae76
124 changed files with 1509 additions and 77 deletions
Binary file not shown.
+1 -1
View File
@@ -1 +1 @@
71b7187c3187e932d5416dd7acff60d60470015ee74b3be9f8d5d5e1469e01d8
d42c35128fdd8ddcefcd2d9883d959faca9801605879bba7a8a2ac6dbfe5794b