From e70742c10fc40de9b674b8aff774375cb8817ec7 Mon Sep 17 00:00:00 2001 From: kdnakt Date: Sat, 14 Oct 2023 22:12:11 +0900 Subject: [PATCH] Fix typo in gradle-tooling.adoc --- docs/src/main/asciidoc/gradle-tooling.adoc | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/src/main/asciidoc/gradle-tooling.adoc b/docs/src/main/asciidoc/gradle-tooling.adoc index 6452911c75704..7f0823dfa77e3 100644 --- a/docs/src/main/asciidoc/gradle-tooling.adoc +++ b/docs/src/main/asciidoc/gradle-tooling.adoc @@ -620,7 +620,7 @@ There are multiple configuration sources that influence Quarkus builds, mentione The Quarkus build uses the `prod` configuration profile: 1. System properties (for example `./gradlew -Dquarkus.package.type=fast-jar ...`) -2. System environment (for example `QUARKUS_PACAKGE_TYPE=fast-jar ./gradlew ...`) +2. System environment (for example `QUARKUS_PACKAGE_TYPE=fast-jar ./gradlew ...`) 3. Configuration via the `quarkus` extensions's `quarkusBuildProperties` For example: quarkus { @@ -748,7 +748,7 @@ TIP: The Quarkus Gradle plugin detects a _CI environment_, if the `CI` environme How the various Quarkus package types are cached in non-CI and CI environments is described in the following table. Note that even if a task's output is not _cached_, the _up-to-date_ checks still apply. -NOTE: The Quarkus application build is split across three tasks. The `quarkusBuild` taskl is responsible to _provide_ +NOTE: The Quarkus application build is split across three tasks. The `quarkusBuild` task is responsible to _provide_ a built Quarkus application. The tasks `quarkusDependenciesBuild` and `quarkusAppPartsBuild` are considered internal tasks (may change at any time w/o prior notice). See below for details.