diff options
| author | 2024-02-01 17:36:57 -0800 | |
|---|---|---|
| committer | 2024-02-02 15:08:46 -0800 | |
| commit | ada543ed86dc4828cecdb937844c6468c872d3e3 (patch) | |
| tree | eba8f7f3d9c15fe6e9ea59f899da7f455aec0f1b /apex/apex.go | |
| parent | 9aa0496c08a0b7c424c0c3b78be37345fb3b0e2c (diff) | |
Print the modules that had strict_updatability_linting set
strict_updatability_linting imposes requirements on all of a module's
transitive dependencies. So you may start getting errors on a module
due to some random other module that is hard to track down. Print out
the modules that caused the current module to use strict updatability
linting so that these errors are easier to debug.
Ignore-AOSP-First: The lint code in internal has diverged from AOSP quite a bit now
Bug: 323366771
Test: m lint-check
Change-Id: I43f2b1adb1ffa5b6e9516694c2bb87c7f94fed7d
Diffstat (limited to 'apex/apex.go')
| -rw-r--r-- | apex/apex.go | 3 |
1 files changed, 2 insertions, 1 deletions
diff --git a/apex/apex.go b/apex/apex.go index 276ac80d5..abab12b35 100644 --- a/apex/apex.go +++ b/apex/apex.go @@ -1104,6 +1104,7 @@ func apexStrictUpdatibilityLintMutator(mctx android.TopDownMutatorContext) { return } if apex, ok := mctx.Module().(*apexBundle); ok && apex.checkStrictUpdatabilityLinting() { + parents := []string{mctx.ModuleName()} mctx.WalkDeps(func(child, parent android.Module) bool { // b/208656169 Do not propagate strict updatability linting to libcore/ // These libs are available on the classpath during compilation @@ -1117,7 +1118,7 @@ func apexStrictUpdatibilityLintMutator(mctx android.TopDownMutatorContext) { return false } if lintable, ok := child.(java.LintDepSetsIntf); ok { - lintable.SetStrictUpdatabilityLinting(true) + lintable.SetStrictUpdatabilityLinting(parents) } // visit transitive deps return true |