mikepenz/AboutLibraries

Support for third_party_licenses files from Google Play Services libraries

开放

#824 创建于 2022年11月29日

 (16 条评论) (1 个反应) (0 位负责人)Kotlin (578 个派生)github user discovery
help wanted

仓库指标

星标
 (4,407 个星标)
PR 合并指标
 (平均合并 5小时 20分钟) (30 天内合并 10 个 PR)

描述

About this issue

Can this plugin also include libraries depended upon by the Google Play services libraries, like the Google oss-licenses-plugin does?

The list of licenses also includes the full license text of any library that is depended upon by the transitive closure of Google Play services libraries used by the app. This means that the list includes any open source libraries that are used to create the Google Play services libraries that are compiled into your app. https://developers.google.com/android/guides/opensource#how-licenses-are-determined

In my case, compared to AboutLibraries, oss-licenses-plugin included additional 17 libraries because of Google Play services, and I'd prefer not to have to maintain it semi-manually and have to keep using oss-licenses-plugin to extract these licenses.

From what I was able to find out, .aar files for Google libraries include third_party_licenses.json and third_party_licenses.txt files that are parsed to extract these libraries and their licenses. Unfortunately in this case there is no "artifact ID" that would correspond to the uniqueId from AboutLibraries, only the name.

As an example of how this looks in the .aar file: https://stackoverflow.com/a/74617118/1916449

Details

  • Used library version: 10.5.2
  • Used support library version
  • Used gradle build tools version
  • Used tooling / Android Studio version
  • Other used libraries, potential conflicting libraries

Checklist

贡献者指南