Uses of Package
io.quarkus.deployment.pkg.builditem
Packages that use io.quarkus.deployment.pkg.builditem
Package
Description
-
Classes in io.quarkus.deployment.pkg.builditem used by io.quarkus.deployment.cmdClassDescriptionThe location that output artifacts should be created in TODO: should we just create them in temp directories, and leave it up to the integration to move them where they want?marker build item that extensions can use to force uber jar creation
-
Classes in io.quarkus.deployment.pkg.builditem used by io.quarkus.deployment.ide
-
Classes in io.quarkus.deployment.pkg.builditem used by io.quarkus.deployment.index
-
Classes in io.quarkus.deployment.pkg.builditem used by io.quarkus.deployment.logging
-
Classes in io.quarkus.deployment.pkg.builditem used by io.quarkus.deployment.pkg.builditem
-
Classes in io.quarkus.deployment.pkg.builditem used by io.quarkus.deployment.pkg.stepsClassDescriptionBuild item to indicate to the various steps that AppCDS generation has been requestedA build item containing the result of the AppCDS generation processRepresents a runnable artifact, such as an uberjar or thin jar.The build systems target directory.The resolved factory for the native image runner.A jar that is build to run the native imageThe location that output artifacts should be created in TODO: should we just create them in temp directories, and leave it up to the integration to move them where they want?Build item that extensions must create to register a package type.Deprecated.A marker build item that is used to indicate that UPX compression was performed
-
Classes in io.quarkus.deployment.pkg.builditem used by io.quarkus.deployment.stepsClassDescriptionBuild item to indicate to the various steps that AppCDS generation has been requestedRepresents a runnable artifact, such as an uberjar or thin jar.The build systems target directory.
-
Classes in io.quarkus.deployment.pkg.builditem used by io.quarkus.deployment.util
ProcessInheritIODisabledBuildItem
instead