diff options
| author |  Greg Estren <gregce@google.com> | 2017-02-17 20:50:03 +0000 |
|---|---|---|
| committer |  Irina Iancu <elenairina@google.com> | 2017-02-20 09:42:52 +0000 |
| commit | 695aeb7493dc0b5ed286e81453a2a9a1364e8322 (patch) | |
| tree | 7fa8eb08bd48696cc8e14980e4edca2a3407a213 /src/main | |
| parent | 1a54aa699c60b131e90598dae9d5226ee9da9399 (diff) | |
Tune naming of Android data binding metadata files.
This puts Bazel in line with the paths actually produced by the data
binding resource processor.
This difference matters when the library name doesn't match the package
name (the build fails without this change).
I started writing a shell integration test to check this end-to-end. But
staging all the data binding support libs and their deps is a mess. Too much
so, IMO.
--
PiperOrigin-RevId: 147868538
MOS_MIGRATED_REVID=147868538
Diffstat (limited to 'src/main')
| -rw-r--r-- | src/main/java/com/google/devtools/build/lib/rules/android/DataBinding.java | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/src/main/java/com/google/devtools/build/lib/rules/android/DataBinding.java b/src/main/java/com/google/devtools/build/lib/rules/android/DataBinding.java index 4d13e039ff..c52bc88938 100644 --- a/src/main/java/com/google/devtools/build/lib/rules/android/DataBinding.java +++ b/src/main/java/com/google/devtools/build/lib/rules/android/DataBinding.java @@ -242,7 +242,7 @@ public final class DataBinding { String.format( "_javac/%s/lib%s_classes/%s/%s-", ruleLabel.getName(), - ruleLabel.getPackageIdentifier().getPackageFragment().getBaseName(), + ruleLabel.getName(), javaPackage.replace('.', '/'), javaPackage); for (String suffix : METADATA_OUTPUT_SUFFIXES) { |