-
Classes Class Description io.quarkus.deployment.builditem.AdditionalStaticInitConfigSourceProviderBuildItem please useStaticInitConfigSourceProviderBuildItem
instead.io.quarkus.deployment.builditem.DevServicesNativeConfigResultBuildItem
-
Fields Field Description io.quarkus.deployment.Capability.METRICS io.quarkus.deployment.dev.testing.TestConfig.basicConsole io.quarkus.deployment.dev.testing.TestConfig.console io.quarkus.deployment.dev.testing.TestConfig.disableColor io.quarkus.deployment.dev.testing.TestConfig.disableConsoleInput io.quarkus.deployment.JniProcessor.JniConfig.enable JNI is always enabled starting from GraalVM 19.3.1.io.quarkus.deployment.pkg.NativeConfig.cleanupServer Since GraalVM 20.2.0 the native image server has become an experimental feature and is disabled by default.io.quarkus.deployment.pkg.NativeConfig.enableJni JNI is always enabled starting from GraalVM 19.3.1.io.quarkus.deployment.pkg.NativeConfig.enableServer This used to be the default prior to GraalVM 20.2.0 and this configuration item was used to disable it as it was not stable. Since GraalVM 20.2.0 the native image server has become an experimental feature.io.quarkus.deployment.pkg.PackageConfig.LEGACY use 'legacy-jar' instead
-
Constructors Constructor Description io.quarkus.deployment.builditem.ArchiveRootBuildItem(Path, Path) io.quarkus.deployment.builditem.CapabilityBuildItem(String) in favor of {@link #CapabilityBuildItem(String, String))} that also accepts the provider of the capability to be highlighted in the error messages in case of detected capability conflicts.io.quarkus.deployment.builditem.JniBuildItem() This method was previously used to enable JNI from Quarkus extensions, but JNI is always enabled starting from GraalVM 19.3.1.io.quarkus.deployment.builditem.nativeimage.ReflectiveHierarchyBuildItem(Type) Use the Builder instead.io.quarkus.runner.bootstrap.AugmentActionImpl(CuratedApplication, List<Consumer<BuildChainBuilder>>)