dependencies still missing with com.google.android.gms.oss-licenses-plugin:0.10.1

See original GitHub issue

Describe the bug Like with com.google.android.gms:oss-licenses-plugin:0.10.0, com.google.android.gms:oss-licenses-plugin:0.10.1 is still thinking that the app does not have any open source licenses. Using com.android.tools.build:gradle:3.5.3 (same problem with 3.5.1), gradle 6.0.1 (same problem with 5.6.0).

To Reproduce Apply any dependency. And try to build.

Expected behavior Three files should get generated by the oss-licenses-plugin, containing all the information needed: app/build/generated/third_party_licenses/res/dependencies.json app/build/generated/third_party_licenses/res/raw/third_party_license_metadata app/build/generated/third_party_licenses/res/raw/third_party_licenses

But the problem is that the two files are generated blank: app/build/generated/third_party_licenses/res/raw/third_party_license_metadata app/build/generated/third_party_licenses/res/raw/third_party_licenses

And the third file gets generated as an empty array: `[

]` app/build/generated/third_party_licenses/res/dependencies.json

Screenshots Screenshot 2020-01-13 at 22 40 08

Desktop (please complete the following information):

Gradle version: 6.0.1 (same problem with 5.6.0)
Android Studio version [e.g. 3.1 (stable)]: 3.5.3
Plugin name and version [e.g. OSS Licenses 16.0.0]: com.google.android.gms.oss-licenses-plugin:0.10.1

Additional context A full list of licenses was generated with com.google.android.gms.oss-licenses-plugin:0.9.5 In case it makes a difference, this is on macOS 10.14.6 but I have also tested on Ubuntu 16.4 with the same result. And also an extra information, I have tried to delete the third_party_libraries directory, to make sure that it is getting recreated and it is. It is still producing the empty files as described above.

Issue Analytics

State:
Created 4 years ago
Reactions:4
Comments:14

Top GitHub Comments

4reactions

caller9commented, Mar 9, 2020

This was released in version 0.10.2. https://developers.google.com/android/guides/releases#march_09_2020

2reactions

hnljpcommented, Jan 21, 2020

@jkasnicki I found the reason for this bug and a possible temporary workaround until it is fixed.

The reason for the problem: https://github.com/google/play-services-plugins/commit/49ac4b435ab0e28fae1238c8852f47511c1dd98c#diff-204bda43e6b03d7ab1af29e3774a40ae

How to temporary work around the bug if you have 3 different product flavors ‘alfa’, ‘bravo’ and ‘charlie’ and two different module ‘yankee’ and ‘zulu’… change from

implementation project(':yankee')
implementation project(':zulu')

alfaImplementation project(':yankee')
bravoImplementation project(':yankee')
charlieImplementation project(':yankee')
alfaImplementation project(':zulu')
bravoImplementation project(':zulu')
charlieImplementation project(':zulu')

Top Results From Across the Web

Include open source notices | Google Play services

When a Maven POM exists for a direct dependency of the app, the plugin processes each <licenses> element and embeds the link and...

How to find gradle plugin id for given gradle library?

oss-licenses-plugin which should be converted to com.google.android.gms.oss.licenses.plugin according to the directory structure and it is not ...

Simple Display of Open Source License Info? | by Nate Ebel

Apply the plugin by adding the following line: apply plugin: 'com.google.gms.oss.licenses.plugin' · Declare the library dependency: compile 'com.google.android.

com.google.android.gms » oss-licenses-plugin » 0.10.5

https://mvnrepository.com/artifact/com.google.android.gms/oss-licenses-plugin --> <dependency> <groupId>com.google.android.gms</groupId> ...

How to list 3rd Party Dependencies Licenses in your Android ...

google.android.gms:oss-licenses-plugin:0.10.5' } } // ...