The Maven home dir is used to resolve the global settings file unless it was explicitly provided on the command line with the -gs argument Here is a list of system properties the Quarkus bootstrap Maven resolver checks during its initialization. See the Native executable guide for more info. Test names *IT and annotated will be run against the native executable.
If you want to test your native executable with Integration Tests, add the following plugin configuration. The build will therefore produce a native executable. Use a specific native profile for native executable building.Įnable the native package type. Tests run: 2, Failures: 0, Errors: 0, Skipped: 0 Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.081 s - in Listening on: 16:52:42,021 INFO (main) Installed features: maven-failsafe-plugin:2.22.0:integration-test (default) quarkus-quickstart-native. If this is set to false, the extension catalog will be narrowed to the defined (or default) platform BOM. Whether or not Quarkus should use the online registry to resolve extension catalogs. The list of extensions to add to the project (comma-separated) The resource path, only relevant if className is set. The fully qualified name of the generated resource It can also accept a version range, in which case the latest from the specified range will be used. The version of the platform you want the project to use. The version currently recommended by the Quarkus Extension Registry The artifact id of the target platform BOM. Not passing it triggers the interactive mode. The following table lists the attributes you can pass to the create command: Attribute