Class CatalogueSource
java.lang.Object
io.github.joke.conventionalversion.CatalogueSource
How either mode reaches the calculated catalogue: the core's only entry point.
Takes a project rather than a settings object, because both modes end at a project. The settings plugin no longer touches the calculation at all - it applies the project plugin to every project, and the project plugin comes here.
-
Field Summary
FieldsModifier and TypeFieldDescriptionprotected static final StringNamed rather than derived, because the name is the identityregisterIfAbsentmatches on and every project has to land on the same one. -
Constructor Summary
Constructors -
Method Summary
Modifier and TypeMethodDescriptionprotected org.gradle.api.provider.Provider<VersionCatalogue> calculate(org.gradle.api.Project project) The project's own directory as the value source's parameter.catalogue(org.gradle.api.Project project) protected org.gradle.api.provider.Provider<VersionCatalogueService> service(org.gradle.api.Project project)
-
Field Details
-
SERVICE_NAME
Named rather than derived, because the name is the identityregisterIfAbsentmatches on and every project has to land on the same one.- See Also:
-
-
Constructor Details
-
CatalogueSource
public CatalogueSource()
-
-
Method Details
-
catalogue
-
service
@VisibleForTesting protected org.gradle.api.provider.Provider<VersionCatalogueService> service(org.gradle.api.Project project) -
calculate
@VisibleForTesting protected org.gradle.api.provider.Provider<VersionCatalogue> calculate(org.gradle.api.Project project) The project's own directory as the value source's parameter. Any directory inside the checkout yields the same answer - the reader resolves the repository root itself - and a project's own directory needs no access to another project's model.
-