java_sdk_library: Path extraction from deps depend on tag
Previously, the information that the java_sdk_library extracted from its child dependencies was determined purely by the type of the dependency and whether it had a tag of the appropriate type. The actual tag itself was ignored. That worked but was a little fragile as it relied on there being no overlap between the types of the dependencies or if there was overlap on the order in which the dependencies were processed and the dependency types were checked to ensure that the correct information was collected. This change makes the information that is extracted dependent on the tag that is used. That makes the behavior much more robust and also simplifes the follow up change which may get the stubs source and API files from separate droidstubs invocations. Changes: * A func field is added to the scopeDependencyTag that is supplied with a dependency from which to extract the information and scopePaths into which the information will be stored. * Each scopeDependencyTag instance supplies its own function. * Various items are renamed to more closely reflect what they actually do. e.g. the apiFileTag is renamed to stubsSourceAndApiTag field because if provides access to both api file and stubs source. Test: m checkapi Bug: 155164730 Merged-In: I4e1861ea67f441f2948a0d7d7053ab0b1169955f Change-Id: I4e1861ea67f441f2948a0d7d7053ab0b1169955f (cherry picked from commit c878250d)
Loading
Please register or sign in to comment