Uses of Package
io.quarkus.registry.config
Packages that use io.quarkus.registry.config
Package
Description
-
Classes in io.quarkus.registry.config used by io.quarkus.registryClassDescriptionRegistry client configuration.Client side registry configuration containing information how to communicate and resolve various catalogs from the registry.
-
Classes in io.quarkus.registry.config used by io.quarkus.registry.clientClassDescriptionClient side registry configuration containing information how to communicate and resolve various catalogs from the registry.
-
Classes in io.quarkus.registry.config used by io.quarkus.registry.client.mavenClassDescriptionClient side registry configuration containing information how to communicate and resolve various catalogs from the registry.Configuration related to the resolution of catalogs of non-platform extensions.Configuration related to the resolution of catalogs of available platforms.
-
Classes in io.quarkus.registry.config used by io.quarkus.registry.configClassDescriptionRegistry client configuration.Top of the config hierarchy.Builder.Base registry catalog artifact configurationAsymmetric data manipulation: Deserialization always uses the builder; Serialization always uses the Impl.Builder.Client side registry configuration containing information how to communicate and resolve various catalogs from the registry.Asymmetric data manipulation: Deserialization always uses the builder.Configuration related to resolution of the registry descriptor.Asymmetric data manipulation: Deserialization always uses the builder; Serialization always uses the Impl.Builder.Registry Maven related configuration the client should use to communicate with the registry.Asymmetric data manipulation: Deserialization always uses the builder; Serialization always uses the Impl.Builder.Registry Maven repository configuration.Asymmetric data manipulation: Deserialization always uses the builder; Serialization always uses the Impl.Builder.Configuration related to the resolution of catalogs of non-platform extensions.Asymmetric data manipulation: Deserialization always uses the builder; Serialization always uses the Impl.Builder.Configuration related to the resolution of catalogs of available platforms.Asymmetric data manipulation: Deserialization always uses the builder; Serialization always uses the Impl.A registry may be configured to accept requests only for the Quarkus versions it recognizes.Asymmetric data manipulation: Deserialization always uses the builder; Serialization always uses the Impl.