You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently we declare dependencies using Kotlin objects residing under buildSrc/.../io.spine.internal.dependency. While this approach works for us, it has a limitation.
When a dependency is used in both buildSrc/build.gradle.kts and in regular build scripts of a project, we have to manually sync. the declarations for each such dependency to make sure the same version is used.
This limitately mabe be overcome when using the Version Catalog feature recently introduced in Gradle. We can publish a settings plugin from the config project, and then use it as a Maven dependency in other projects.
Currently we declare dependencies using Kotlin objects residing under
buildSrc/.../io.spine.internal.dependency
. While this approach works for us, it has a limitation.When a dependency is used in both
buildSrc/build.gradle.kts
and in regular build scripts of a project, we have to manually sync. the declarations for each such dependency to make sure the same version is used.This limitately mabe be overcome when using the Version Catalog feature recently introduced in Gradle. We can publish a settings plugin from the
config
project, and then use it as a Maven dependency in other projects.More info on Version Catalog feature from Cédric Champeau.
The text was updated successfully, but these errors were encountered: