davsclaus opened a new pull request, #28886: URL: https://github.com/apache/camel/pull/28886
_Claude Code on behalf of davsclaus_ ### Why The "Package-native validation" workflow builds only the jbang modules and `camel-launcher` from source (`-pl` without `-am`). Their other in-repo dependencies come from the published apache snapshot. `camel-jbang-core` calls the API of `camel-yaml-dsl-validator` (`ProjectFacts` and others). The AI tools work keeps changing both modules in the same PR. Until the next snapshot deploy, every PR that triggers this workflow then fails to compile `camel-jbang-core`. This happened on #28885 after #28849 added an argument to the `ProjectFacts` constructor: ``` ValidatorFacts.java:[74,16] no suitable constructor found for ProjectFacts(...) ``` ### Change `dsl/camel-yaml-dsl/camel-yaml-dsl-validator` is added to the `-pl` list of both jobs (POSIX and Windows), and the comment explains why. The module has no build plugins of its own and is built with `-DskipTests`, so it adds little build time. Its own dependencies (catalog, yaml-dsl, xml-io) still come from the snapshot. ### Tested `./mvnw -P apache-snapshots -pl dsl/camel-yaml-dsl/camel-yaml-dsl-validator,dsl/camel-jbang/camel-jbang-core compile -Dcamel.skipDocSamples=true` passes on main. This PR touches the workflow file, so the workflow runs on it. 🤖 Generated with [Claude Code](https://claude.com/claude-code) https://claude.ai/code/session_016Y4dDiMc7mxmdVoQiGSMh8 -- 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]
