Closed calvarez-ov closed 3 years ago
androidx.annotation
and androidx.preference
not getting added to the dependencies node of the pom file was a bug.
Also, realized that androidx.legacy:legacy-support-v4
was not being used anywhere in the project - removed it.
Agreed, that for the same version of the library - dependencies should be identical. Will ensure that doesn't happen going forward.
Version 1.1.5 is now live on MavenCentral.
Describe the bug Our builds are failing since this morning, because of an apparent change in the pom dependencies from trust kit. We have a check in our build to be sure we know of all dependencies that are pulled into our project transitively. It started failing today because there's a new transitive dependency being pulled in by trustkit:
androidx.legacy:legacy-support-v4.
To Reproduce Steps to reproduce the behavior. Look at the pom file on jcenter. There are no
<dependencies>
:Look at the pom file on maven central. There are three
<dependency>
s:Expected behavior For the same version of the library (1.1.3), the dependencies should be identical, regardless of whether the library is hosted on jcenter or maven central.
Actual behavior: dependencies are different.