Red Hat’s Build of Quarkus 3.2 Introduces Enhanced UI for Java Development and New Pact Tool
Red Hat’s latest iteration of the Quarkus Kubernetes-native Java stack introduces significant enhancements, including a revamped developer UI and a robust contract-based testing capability. Released under the Red Hat build of Quarkus version 3.2, unveiled on October 23, developers can now access these new features through developers.redhat.com.
The Developer UI in Quarkus 3.2 brings improvements such as streamlined menu navigation, enhanced configuration file management, continuous testing management tools, and insights into build information. Additionally, developers can now view detailed information about development services. For contract-based testing, the 3.2 build integrates the Pact tool, facilitating HTTP and message integration tests through contract-based testing methodologies. Pact can seamlessly integrate into existing testing and deployment workflows.
Quarkus, an open-source project designed to empower Java developers in building cloud-native applications, supports both HotSpot and GraalVM virtual machines. It aims to elevate Java’s position in Kubernetes and serverless environments while enabling developers to leverage diverse distributed application architectures.
The command-line interface (CLI) in Red Hat Quarkus 3.2 now boasts close to 30 commands, enabling developers to create projects, manage extensions, and execute essential build and development tasks seamlessly. Notably, the new Quarkus deploy command simplifies application deployment to platforms like Kubernetes, Knative, and Red Hat OpenShift without requiring changes to project dependencies or configurations.
Specifically tailored for Kubernetes environments, Quarkus 3.2 introduces a new development service designed for Kubernetes deployments. This service simplifies the setup and configuration of a Kubernetes API server in development mode, essential for running tests using Docker containers. Additionally, a service discovery mechanism facilitates seamless interaction between Quarkus applications running in development mode within a Kubernetes cluster.
The command-line tool in the Red Hat Quarkus 3.2 build now has nearly 30 commands to create projects, manage extensions, and perform essential build and dev commands. A Quarkus deploy command in the CLI enables deployment of Quarkus applications to platforms such as Kubernetes, Knative, and Red Hat OpenShift with no changes to project dependencies or configuration.
Kubernetes-native features include a new dev service for Kubernetes deployments. This service starts and configures a Kubernetes API server in dev mode and when running tests using Docker. A service discovery mechanism is also implemented for Quarkus applications running in dev mode to share a cluster.