ppalaga edited a comment on issue #2276: URL: https://github.com/apache/camel-quarkus/issues/2276#issuecomment-783265388
Thanks for the report, I was able to reproduce. It pops up by JFR, because it is the only JVM-only extension that has a custom Quarkus config. The metadata of that config is generated via `io.quarkus.annotation.processor.ExtensionAnnotationProcessor` that in turn is invoked via compiler plugin. As it happens, ExtensionAnnotationProcessor does not produce the metadata when `-Dquickly` is set : https://github.com/quarkusio/quarkus/commit/ce37fb412ec93dda8c56ae66a6af7e2aeacb3c71 so your first maven command does not generate it. Then the second command does not help either because there is no change in the source tree, so the compilation is effectively skipped: ``` [INFO] --- maven-compiler-plugin:3.8.0:compile (default-compile) @ camel-quarkus-jfr --- [INFO] Nothing to compile - all classes are up to date ``` ... and thus `update-extension-doc-page` fails because it does not find the metadata file. As a solution, I suggest to add `-Dcamel-quarkus.update-extension-doc-page.skip` to your second maven commad. I assume, you do not care for the doc pages. You only want to run the JVM tests ---------------------------------------------------------------- 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. For queries about this service, please contact Infrastructure at: [email protected]
