diff options
| author | 2019-09-27 00:38:03 +0900 | |
|---|---|---|
| committer | 2019-09-27 01:50:46 +0900 | |
| commit | d15aa1f1233aa1b51470fc09b024f1844ea33f8f (patch) | |
| tree | 515c05b91dae320343de2fc6246bbd3673d3ea89 /java/java.go | |
| parent | 5e493d5660e0fffede935354a17c2f31dba46b83 (diff) | |
respect "apex_name:" for "apex" module
For now, apex_name is used only for flattened apex.
Even if apex_name is set, the activation point of unflattened is
determined by 'name' in apex_manifest.json.
This change make apex_name as priority.
If apex_name is set, then use this for apex name
- update name in apex_manifest.json to apex_name
- do not check if key filename matches (use apex_name as key name)
This can be useful if soong wants to rename apex module. Simply setting
apex_name has the same effect of renaming "activation point" of apex.
But: 139774701
Test: m (soong test)
Change-Id: I8ea3645e4aa8f317997bc1443ec308ed0595b1c2
Diffstat (limited to 'java/java.go')
0 files changed, 0 insertions, 0 deletions