0xera
0xera
So I think this maybe happen because some vendor do something with sqlite for optimization. Maybe for fix add to exoplayer opportunity to use other databases or sqlite from Jetpack?
@vaibhav-sharechat did you fix this?
Hello. Try to add google repository in your plugin management like this https://github.com/deepmedia/Grease/blob/eed3781f871e99940230e9b9b65e12a3db510ac2/settings.gradle.kts#L3
I tried to publish the library with compileOnly and the dependency did not appear in the pom file. I also found this discussion https://discuss.gradle.org/t/publishing-plugin-should-respect-compileonly-configuration/22903 And checked old fat aar plugins...
No, i could not reproduce #11. Also author says first crash does not happen anymore
I have found why there is a problem with META-INF. It is because shadow jar uses Gradle Api from 8.3 version, so building a library with lower version than 8.3...
Hi, @natario1 I have added a functional test and you can run it to make sure that compileOnly dependencies are not in a pom file
I dont have any other idea, so i have just added api configuration for special cases when we need include aidl parcelables from project dependencies in fat aat
@natario1 what do you think about this solution?