AboutLibraries automatically collects all dependencies and licenses of any gradle project (Kotlin MultiPlatform), and provides easy to integrate UI components for Android and Compose-jb environments
I've noticed that some libraries, that are reported by gradle when running ./gradlew app:dependencies --configuration debugRuntimeClasspath are missing from the report
How can the issue be reproduced / sample code
I'm joining a minimal sample project to reproduce:
MissingLib.zip
It's an app that does nothing but display the list of dependencies using AboutLibraries.
Within the sample project, run ./gradlew app:dependencies --configuration debugRuntimeClasspath
Notice that there are 3 androidx.annotation:annotation libraries:
androidx.annotation:annotation
androidx.annotation:annotation-jvm
androidx.annotation:annotation-experimental
Run ./gradlew app:findLibraries
Notice that there are only 2 of the androidx.annotation:annotation libraries:
About this issue
Briefly describe the issue
I've noticed that some libraries, that are reported by gradle when running
./gradlew app:dependencies --configuration debugRuntimeClasspath
are missing from the reportHow can the issue be reproduced / sample code
I'm joining a minimal sample project to reproduce: MissingLib.zip It's an app that does nothing but display the list of dependencies using AboutLibraries.
./gradlew app:dependencies --configuration debugRuntimeClasspath
androidx.annotation:annotation
libraries:./gradlew app:findLibraries
androidx.annotation:annotation
libraries:Potential fix
I experimented with the plugin, and what should fix it is to modify this line: https://github.com/mikepenz/AboutLibraries/blob/develop/plugin-build/plugin/src/main/kotlin/com/mikepenz/aboutlibraries/plugin/util/DependencyCollector.kt#L129
From:
to
It doesn't seem to have any negative side effect to do so, but maybe I'm missing something?
Let me know if I can/should open a merge request.
Details
Checklist