-
Bug
-
Resolution: Done
-
Major
-
2.2.5.GA
-
False
-
False
-
+
-
-
Quarkus Docs Sprint 2, Quarkus Docs Sprint 3, Quarkus Docs Sprint 4, Quarkus Docs Sprint 5
- Get rid of <quarkus-plugin.version> in the pom.xml examples{}
Generated projects now referencing only <quarkus.platform.version>. The <quarkus.platform.version> should be used to reference versions of extensions, plugins in examples provided. The <quarkus-plugin.version> should be removed entirely.
- Wrong default native builder image specified{}
Red Hat build of Quarkus 2.2 uses registry.access.redhat.com/quarkus/mandrel-20-rhel8:21.2 registry.access.redhat.com/quarkus/mandrel-21-rhel8:21.2
To verify: grep -rnw . -e quarkus.native.builder-image (run inside maven repository)
- Chapter 3 remove -DclassName from the default command
Minimal command needed to generate Quarkus project can do so without `-DclassName` option. This option can be removed from the command and description. This command is listed in the following table is enough.
- Chapter 3 wrong default value of the ${projectGroupId}
Default value of the projectGroupId is org.acme
-
-
- Only if interactive create command was used with no codestarts
-
- Chapter 3 wrong default value of the ${className}{}
Default value of the className is ${projectGroupId}/GreetingResource.java
-
-
- Only if interactive create command was used with no codestarts
-
- Chapter 4 is missing a code snippet for the surefire plugin
Because surefire properties are mentioned there and described it should contain snippet for surefire plugin configuration
- Chapter 11 quarkus-bootstrap:build-tree was substituted by quarkus:dependency-tree
https://github.com/quarkusio/quarkus/issues/22186
The next are some text improvements:
Tests that include IT in their names are annotated @NativeImageTest are run against the native executable.{}
Tests that include IT in their names and annotated with @NativeImageTest are run against the native executable.
- Use either word "Expand" or "Extract" in the tutorial text (talking about unzipping archive)
To build a native application, add a specific native profile that includes the Maven Surefire and Maven Failsafe plug-ins
To build a native application, add a specific native profile that includes Maven Failsafe plug-in (because the next command is not referencing the surefire plugin and it should not)
The Quarkus Maven repository contains many of the requirements that Java developers typically use to build their applications
The Quarkus Maven repository contains many of the dependencies that Java developers typically use to build their applications
- Online maven repository{}
Two sentences:
1. You can use the online Quarkus repository with your Quarkus Maven project
2. You can use the online Maven repository with your Quarkus projects
By saying online Maven repository you mean Red Hat's hosted online repository. These two sentences may confuse some people. Because this is a productized guide it should be clear that Red Hat's hoster repository is meant by that.
NATIVE EXECUTABLE PART of the guide
- Change the hyperlink inside Universal Base Image (UBI) note (Chapter 12.1) to point to the right location of those images.
- account is impacted by
-
QUARKUS-1389 Doument developing and compiling your Quarkus applications with Apache Maven
-
- Closed
-
- impacts account
-
QUARKUS-1386 Document compiling your Quarkus applications to native executables guide
-
- Closed
-
- mentioned on