All Classes and Interfaces
Class
Description
This implementation isn't currently used but is kept for testing purposes.
Utility for merging catalog data.
Asymmetric data manipulation:
Deserialization always uses the builder;
Serialization always uses the Impl.
Builder.
Asymmetric data manipulation:
Deserialization always uses the builder;
Serialization always uses the Impl.
Builder.
Asymmetric data manipulation:
Deserialization always uses the builder;
Serialization always uses the Impl.
Builder.
Asymmetric data manipulation:
Deserialization always uses the builder;
Serialization always uses the Impl.
Builder.
Serialization detail.
Serialization detail.
Serialization detail.
Serialization detail.
Serialization detail.
Make sure a JsonBuilder is built before being serialized
Serialization detail.
Extension origin preference
Asymmetric data manipulation:
Deserialization always uses the builder;
Serialization always uses the Impl.
Builder.
Asymmetric data manipulation:
Deserialization always uses the builder;
Serialization always uses the Impl.
Builder.
Platform release
Asymmetric data manipulation:
Deserialization always uses the builder;
Serialization always uses the Impl.
Builder.
Representation of Quarkus Platform release.
Asymmetric data manipulation:
Deserialization always uses the builder;
Serialization always uses the Impl.
Builder.
Registry client configuration.
Top of the config hierarchy.
Builder.
A helper class set utility methods to locate the registry client configuration file
in the default locations (e.g. user home
.quarkus dir, or the project dir) or in
at the location specified by the caller.Base registry catalog artifact configuration
Asymmetric data manipulation:
Deserialization always uses the builder;
Serialization always uses the Impl.
Builder.
Implements the basic queries a registry client is supposed to handle.
Registry client factory service provider interface that will be looked up on the class path using the ServiceLoader
mechanism.
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.
Builder.
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.
Builder.