[
https://issues.apache.org/jira/browse/CAMEL-23326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18146144#comment-18146144
]
Guillaume Nodet commented on CAMEL-23326:
-----------------------------------------
This issue is being investigated by a coding agent (on behalf of gnodet).
Code analysis confirms the issue: the incremental-build.sh EXCLUSION_LIST is
missing 5 modules that always get pulled in via -amd due to transitive
dependencies on camel-catalog:
- camel-jbang-mcp (Quarkus-based, depends on camel-catalog aggregator)
- camel-jbang-plugin-validate (depends on camel-yaml-dsl-validator ->
camel-catalog)
- camel-launcher-container (pom module depending on camel-launcher)
- camel-yaml-dsl-validator (depends on camel-catalog)
- camel-yaml-dsl-validator-maven-plugin (depends on camel-yaml-dsl-validator)
Note: camel-jbang-plugin-route-parser was already removed from the codebase
(CAMEL-25587), so it no longer applies.
Fix: add these 5 artifact IDs to the EXCLUSION_LIST in
.github/actions/incremental-build/incremental-build.sh.
_Note: This comment was generated by an AI coding agent and requires manual
verification._
> [build] Exclude common components from regular testing
> ------------------------------------------------------
>
> Key: CAMEL-23326
> URL: https://issues.apache.org/jira/browse/CAMEL-23326
> Project: Camel
> Issue Type: Task
> Reporter: Pasquale Congiusti
> Assignee: Guillaume Nodet
> Priority: Major
>
> When we automatically have CI test for GitHub PR, the incremental test script
> includes automatically certain modules that are not really directly dependant
> from the module we're changing and that we want to test. As an example, these
> are the modules we always test:
> Camel :: JBang :: MCP
> Camel :: JBang :: Plugin :: Route Parser
> Camel :: JBang :: Plugin :: Validate
> Camel :: Launcher :: Container
> Camel :: YAML DSL :: Validator
> Camel :: YAML DSL :: Validator Maven Plugin
> This is due to the fact that we have certain modules that require an explicit
> dependency from all other modules. In the previous versions of the testing
> action we developed, we had an hardcoded list of modules to exclude (exactly
> the ones listed here) for that reason. I suggest we recover that part so we
> have a cleaner action.
> From a design point of view it would be nice we decouple those dependencies
> in order to avoid a strict dependency chaining, but this may require deeper
> changes. At least as an immediate action I suggest to denylist those known
> common components.
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)