Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix typo in gradle-tooling.adoc #36485

Merged
merged 1 commit into from
Oct 14, 2023
Merged

Fix typo in gradle-tooling.adoc #36485

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions docs/src/main/asciidoc/gradle-tooling.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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 {
Expand Down Expand Up @@ -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.

Expand Down