aboutsummaryrefslogtreecommitdiffhomepage
path: root/third_party/grpc/compiler
diff options
context:
space:
mode:
authorGravatar Googler <noreply@google.com>2017-05-30 21:55:11 +0200
committerGravatar László Csomor <laszlocsomor@google.com>2017-05-31 09:19:45 +0200
commit886a80ff71e53d7035056df8099950426c109c33 (patch)
tree0bc0157615130b6c443cc99d9b49438c893a8fac /third_party/grpc/compiler
parent3834dc87953638aa818257cad5e8692d97fc7532 (diff)
When filtering resources in analysis, also filter resource roots
If all resources from a directory are filtered out, the resource processing action should not receive a reference to that directory. Filtering the entire contents of a directory is uncommon but not impossible. It may be indicative of an error (if the user filters on a language, but only provided resources in other languages - in this case, the build should and will fail during Java compilation when the requested resource does not exist) or of weird but acceptable behavior (placing resources for some default language in one resource directory and resources for all other languages in some other directory, then inheriting both directories and filtering on language) that should be correctly handled. RELNOTES: none PiperOrigin-RevId: 157499745
Diffstat (limited to 'third_party/grpc/compiler')
0 files changed, 0 insertions, 0 deletions