jamesnetherton commented on code in PR #8156: URL: https://github.com/apache/camel-quarkus/pull/8156#discussion_r2698970351
########## docs/modules/ROOT/pages/contributor-guide/index.adoc: ########## @@ -46,7 +46,11 @@ A build with integration tests in both the JVM mode and the native mode: mvn clean install -Pnative ---- -TIP: You may want to install and use https://github.com/mvndaemon/mvnd[`mvnd` - the Maven Daemon] for faster builds. +TIP: You may want to install and use https://github.com/mvndaemon/mvnd[`mvnd` - the Maven Daemon] for faster builds. When using `mvnd` on MacOS, make sure the mvnd version matches your installed Maven version (`mvn`) to avoid compilation failures due to missing dependencies. + +TIP: For building native images on MacOS, you usually **do not need** to use `-Dquarkus.native.container-build`. This option is primarily intended for Linux systems, where the native image build runs inside a Docker container. On MacOS, GraalVM can typically generate the native image directly, so omitting this option simplifies the build and avoids unnecessary errors. + +TIP: Some extensions may not yet support native image generation on MacOS. If an integration test fails when running `mvnd clean install -Dnative` due to failure to build the native image, this is expected and not necessarily a problem with your environment. Running the same test in JVM mode (`mvn clean install`) should work correctly. Review Comment: I think we should be explicit about what we expect to fail with MacOS native builds. IIRC that's currently just limited to extensions that require AWT. ```suggestion TIP: Extensions that depend on Java AWT are not yet supported for native image generation on MacOS. If an integration test fails when running `mvnd clean install -Dnative` due to missing AWT support, this is expected and not necessarily a problem with your environment. Running the same test in JVM mode (`mvn clean install`) should work correctly. ``` -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
