Most subprojects in Archie define their dependencies as api dependencies, while in some cases just implementation would be enough (see also API and implementation separation in the Gradle documentation).
Having dependencies declared as api dependencies can make it harder to change or remove these dependencies, as users of Archie may rely on them being present.
We should check all subprojects and change the dependencies to implementation where possible. This should be done for both external dependencies on third-party libraries and internal dependencies on other Archie subprojects.
Also a lot of dependencies are added to all subprojects in the main build.gradle file. These should be moved to only the subprojects that need them.
Most subprojects in Archie define their dependencies as
apidependencies, while in some cases justimplementationwould be enough (see also API and implementation separation in the Gradle documentation).Having dependencies declared as
apidependencies can make it harder to change or remove these dependencies, as users of Archie may rely on them being present.We should check all subprojects and change the dependencies to implementation where possible. This should be done for both external dependencies on third-party libraries and internal dependencies on other Archie subprojects.
Also a lot of dependencies are added to all subprojects in the main
build.gradlefile. These should be moved to only the subprojects that need them.