diff options
| author |  asteinb <asteinb@google.com> | 2018-05-03 08:09:09 -0700 |
|---|---|---|
| committer |  Copybara-Service <copybara-piper@google.com> | 2018-05-03 08:10:55 -0700 |
| commit | 158dda74f4d6d33b88be4ab4c40322eca5f1c2fd (patch) | |
| tree | 9d666848416b0b59328c2e6e3b11e221be1f3905 /WORKSPACE | |
| parent | 70821069b0e39249eb0f23cf16ca4438c9703a7b (diff) | |
Fix up newly discovered bugs in decoupled Android data processing
- Always generate a symbols file - the new resource processing pipeline likes
knowing that this is non-null, and it shouldn't cost much extra to create.
- A misleading method signature (which I made) led to me forgetting about
Proguard artifacts. Properly propogate them into the ResourceApk object.
- Don't get Aapt version directly from AndroidConfiguration - there's some
additional logic in AndroidAaptVersion not exposed elsewhere
- Split library tests that expect resources and assets to be processed together
to have a new version where they're processed seperately.
- Tests use ValidatedAndroidData interface rather than ResourceContainer object
- Properly move some LocalTest magic around resource JAR out of the old
pipeline only, as it should apply to both old and new pipelines.
- Processing action defaults to empty resource and asset deps rather than null
RELNOTES: none
PiperOrigin-RevId: 195253161
Diffstat (limited to 'WORKSPACE')
0 files changed, 0 insertions, 0 deletions