List the build tools supported by Quarkus?

Quarkus supports the two build tools most Java teams already use day to day, rather than requiring a new or proprietary build system.

• Maven: the most common choice, using the quarkus-maven-plugin for project scaffolding, dev mode, and native builds via profiles or plugin goals.
• Gradle: supported via the io.quarkus Gradle plugin, with equivalent tasks for running dev mode (quarkusDev) and building native images.

Both integrate the same underlying Quarkus build process — the build-time augmentation phase that scans extensions, resolves configuration, and (for native builds) invokes GraalVM's native-image tool — so the choice between Maven and Gradle is really about which build tool a team already standardizes on, not a difference in what Quarkus itself can do.

The Quarkus CLI adds a third, tool-agnostic layer on top of either: commands like quarkus dev or quarkus build detect whether the project is Maven- or Gradle-based and delegate to the right underlying build tool automatically.