[ 
https://issues.apache.org/jira/browse/CAMEL-23326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Guillaume Nodet reassigned CAMEL-23326:
---------------------------------------

    Assignee: Guillaume Nodet

> [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)

Reply via email to