Apex_available check failure reveals dependency
When the check for apex_available has failed, the build system now shows
the module that brought the unavailable module into the APEX.
Bug: 151051671
Test: m
Merged-In: Id1a3fda67fe56fdc2dc90ec800d10689415de4d6
(cherry picked from commit 7bd9444b0fb928b7c05d50376f22e37a961bb499)
Change-Id: Id1a3fda67fe56fdc2dc90ec800d10689415de4d6
diff --git a/apex/apex.go b/apex/apex.go
index de18e5c..5a5c02f 100644
--- a/apex/apex.go
+++ b/apex/apex.go
@@ -2000,7 +2000,7 @@
if externalDep || to.AvailableFor(apexName) || whitelistedApexAvailable(apexName, to) {
return
}
- ctx.ModuleErrorf("requires %q that is not available for the APEX.", to.Name())
+ ctx.ModuleErrorf("%q requires %q that is not available for the APEX.", from.Name(), to.Name())
})
}