summaryrefslogtreecommitdiff
path: root/tools/aapt2/java/JavaClassGenerator.cpp
diff options
context:
space:
mode:
authorEliot Courtney <edcourtney@google.com>2017-12-14 19:57:51 +0900
committerEliot Courtney <edcourtney@google.com>2017-12-26 17:22:15 +0900
commit6c313d3224c878d832db3ed833f4a3dd3786fb1f (patch)
tree8ef78ae86f01b1fd6b28b9c675dfefb4b499d0c9 /tools/aapt2/java/JavaClassGenerator.cpp
parent4a96b36fd9857cd3d3534ed0396ec3d7155a324c (diff)
Initialise Notification*Manager dependencies directly.
Currently, adding a new dependency to any of these classes means updating the constructors of any subclasses, and the construction in the corresponding SystemUIFactory classes and subclasses. In particular, updating these in separate vendor/ projects is annoying. So, initialise the dependencies using field initialisers. The downside is that it's harder to notice circular Dependencys. Bug: 63874929 Bug: 62602530 Test: runtest systemui Test: Compile and run Change-Id: I21d58d0cc0edeb6d53fb7b387c9baeec7bd80589
Diffstat (limited to 'tools/aapt2/java/JavaClassGenerator.cpp')
0 files changed, 0 insertions, 0 deletions