summaryrefslogtreecommitdiff
path: root/tools/aapt2/java/JavaClassGenerator_test.cpp
diff options
context:
space:
mode:
authorJiyong Park <jiyong@google.com>2020-02-01 17:16:58 +0900
committerJiyong Park <jiyong@google.com>2020-02-01 18:07:57 +0900
commit963ee178c993b77fe75ac4d104b4fa16c7bcdc08 (patch)
treea316bf3b01474b4c54300a622f84b34e172c905f /tools/aapt2/java/JavaClassGenerator_test.cpp
parent7ba51f4f9e9702c2237051efe9dab50c9f05fb90 (diff)
Don't build framework-annotation-proc with framework.jar
Previously, framework-annotation-proc was built with framework.jar in its classpath. This was because sdk_version is not set for the module, in which case the build system automatically add framework.jar to the classpath. This is wrong because the classes from framework.jar are also provided via the srcs property of framework-annotation-proc. With this setup, a build error could happen when there is a jarjar'ed class. The class is jarjar'ed in framework.jar, while the same class in source files isn't jarjar'ed yet when compiling it. To fix the problem, remove framework.jar out of classpath by setting sdk_version to core_platform and provide additional libraries via libs property. Bug: N/A Test: m Change-Id: I00974c76aaa0ce40384ffa6bf13d4f0ba5e37954
Diffstat (limited to 'tools/aapt2/java/JavaClassGenerator_test.cpp')
0 files changed, 0 insertions, 0 deletions