ppalaga opened a new issue, #4393: URL: https://github.com/apache/camel-quarkus/issues/4393
Follows up https://github.com/apache/camel-quarkus/pull/4385/files#diff-fa25b87249559ee321efea1b839659150f97ca18cf5718cab8826bde025d7a84R52-R67 While this is fine for this initial version of the Groovy DSL support, we should not leave it as is in the long term. We generally do not want end users to add any GraalVM extra flags. Our extensions should be able to configure everything needed. However, `--allow-incomplete-classpath` and `--report-unsupported-elements-at-runtime` are special: we should try to always avoid them. The reason is that they hide potential problems that may make the app fail at runtime. The root cause of why `--report-unsupported-elements-at-runtime` is required in some situations needs to be understood in order to be able to tell whether this is an issue of how Camel Quarkus or Camel is using Groovy or whether this is an issue fixable in Groovy (how about Groovy 4?) or whether we should seek for a fix in GraalVM. Once a tracker issue is created in any external project, its reference should be pasted to `docs/modules/ROOT/pages/reference/extensions/groovy-dsl.adoc` -- 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]
