@@ -33,7 +33,7 @@ buildscript {
33
33
}
34
34
dependencies {
35
35
// We don't apply any plugins.
36
- // We just put our code on a classpath of settings script.
36
+ // We just put `SpineVersionCatalog` class on a classpath of settings script.
37
37
classpath(" io.spine.internal:spine-version-catalog:+" )
38
38
}
39
39
}
@@ -42,13 +42,14 @@ dependencyResolutionManagement {
42
42
versionCatalogs {
43
43
44
44
/*
45
- The code, we have put on a classpath, exposes a class `SpineVersionCatalog`,
46
- which can execute actions upon `VersionCatalogBuilder`.
45
+ `SpineVersionCatalog` is not a plugin, it just exposes a method, which
46
+ operates upon Gradle's provided `VersionCatalogBuilder`, filling it up
47
+ with items.
47
48
48
49
It is so because we want to preserve a possibility of overwrite.
49
50
Currently, Gradle does not provide a clear way to perform overwrite for
50
- already created catalogs. Thus, it is a responsibility of end-users
51
- to create catalogs. `SpineVersionCatalog` just operates upon the given builder .
51
+ ALREADY CREATED catalogs. Thus, a plugin can't create the catalog, and
52
+ it's a responsibility of end-users to it .
52
53
53
54
In order to override a version, shipped by the catalog, one should
54
55
declare it BEFORE applying the catalog to the builder. Versions,
@@ -80,7 +81,7 @@ dependencyResolutionManagement {
80
81
version(" kotlin" , " 1.5.31" )
81
82
version(" kotlinX-coroutines" , " 1.5.2" )
82
83
83
- // Fills up this catalog with our dependencies .
84
+ // Fills up this builder .
84
85
SpineVersionCatalog .useIn(this )
85
86
}
86
87
}
0 commit comments