diff options
| author | Jiyong Park <jiyong@google.com> | 2020-01-06 13:25:22 +0900 |
|---|---|---|
| committer | Anton Hansson <hansson@google.com> | 2020-01-10 15:15:47 +0000 |
| commit | ee758131624170b9083a324de53c4afd79320531 (patch) | |
| tree | a0b94e192113c0abff79a63e4507f68cc684eab1 /buildspec.mk.default | |
| parent | c30b734f427915ecc92677017b71d6e005d806bf (diff) | |
| download | platform_build-ee758131624170b9083a324de53c4afd79320531.tar.gz platform_build-ee758131624170b9083a324de53c4afd79320531.tar.bz2 platform_build-ee758131624170b9083a324de53c4afd79320531.zip | |
Correctly gather boot jars from APEXes
Jars in APEXes have Make module names <jar_name>.<apex_name>. e.g.
updatable-apex.com.android.media. Previously, we have used <jar_name>
which actually meant the platform variant of the jar. This is not only
incorrect, but also is causing problem as the platform variant is no
longer available when the jar is configured to be available only for the
corresponding APEX (via the apex_available property).
Fixing the problem by correctly using <jar_name>.<apex_name> scheme.
Bug: N/A
Test: m
Change-Id: I6e255ce88c9bd80120b29197fb2637a64010f531
Merged-In: I6e255ce88c9bd80120b29197fb2637a64010f531
Diffstat (limited to 'buildspec.mk.default')
0 files changed, 0 insertions, 0 deletions