diff options
| author | Jiyong Park <jiyong@google.com> | 2018-10-10 14:05:29 +0900 |
|---|---|---|
| committer | Jiyong Park <jiyong@google.com> | 2018-10-11 14:24:32 +0900 |
| commit | ab3ceb38552c69b8042b75c95b2826c8ecf413e5 (patch) | |
| tree | 243c8217d111348769694cf28535b533c39c02cb /java/java.go | |
| parent | 48ca7dc5352d3e65cd927bcae7cb861d6c0f500c (diff) | |
Make APEX build rules consistent
Don't directly iterate over the copyManifest map to generate the copy
commands. Iterating over a map in golang isn't guaranteed to give
consistent order. This causes the apex build rules to be executed even
when there is no source file change.
Fix the issue by creating a sorted list of the key and then iterate over
the list.
Bug: 117453592
Test: m apex.test; m.apex.test nothing is built during the second
build
Change-Id: I329a91ec0b6a34cbe745bf9a9ceb0843b63c200c
Diffstat (limited to 'java/java.go')
0 files changed, 0 insertions, 0 deletions