@@ -598,7 +598,7 @@ invoke Maven's `verify` goal with `-DskipITs=false -Dquarkus.test.integration-te
598598generate the native image configuration.
599599For example:
600600
601- [source,bash]
601+ [source,bash,subs=attributes+ ]
602602----
603603$ ./mvnw verify -DskipITs=false -Dquarkus.test.integration-test-profile=test-with-native-agent
604604...
@@ -660,7 +660,7 @@ This can be useful to verify that the native integration tests work as expected,
660660assuming that the JVM unit tests have generated the correct native image configuration.
661661The typical workflow here would be to first run the integration tests with the native image agent as shown in the previous section:
662662
663- [source,bash]
663+ [source,bash,subs=attributes+ ]
664664----
665665$ ./mvnw verify -DskipITs=false -Dquarkus.test.integration-test-profile=test-with-native-agent
666666...
@@ -671,7 +671,7 @@ $ ./mvnw verify -DskipITs=false -Dquarkus.test.integration-test-profile=test-wit
671671And then request a native build passing in the configuration apply flag.
672672A message during the native build process will indicate that the native image agent generated configuration files are being applied:
673673
674- [source,bash]
674+ [source,bash,subs=attributes+ ]
675675----
676676$ ./mvnw verify -Dnative -Dquarkus.native.agent-configuration-apply
677677...
@@ -702,7 +702,7 @@ and confirm that the class and/or package making the call or being accessed is n
702702If the missing entry is related to some resource,
703703you should inspect the Quarkus build debug output and verify which resource patterns are being discarded, e.g.
704704
705- [source,bash]
705+ [source,bash,subs=attributes+ ]
706706----
707707$ ./mvnw -X verify -DskipITs=false -Dquarkus.test.integration-test-profile=test-with-native-agent
708708...
0 commit comments