Remove test classes from test-infra, and include everything under main#21577
Remove test classes from test-infra, and include everything under main#21577Croway merged 2 commits intoapache:mainfrom
Conversation
0cbdca1 to
f8f176f
Compare
|
🌟 Thank you for your contribution to the Apache Camel project! 🌟 🐫 Apache Camel Committers, please review the following items:
|
|
@davsclaus @jamesnetherton @oscerd there are Camel projects that uses the test-jar test-infra dependencies
These project need to be updated, in particular, the test-infra test-jar dependencies has to be removed, and only the test-infra dependencies with test scope should be used instead. |
|
awesome I had problemes with that test-jar surprise recently - nice its just a normal JAR |
|
most probably camel-quarkus is not an issue @jamesnetherton is it right? camel-quarkus is not using camel test-infra test-jars |
|
you are welcome to create a github ticket for CKC so its not forgotten there - though we dont have bandwith to maintain this project. |
|
4.19 upgrade doc needs to be updated |
|
I am aligning CKC and Camel Spring Boot, I do hope CKC mvn verify will work on the first try |
|
camel kafka connector main is using camel 4.14, I won't update it than, if camel kafka connector will be updated to camel 4.19+, the changes to be done will be mentioned in the upgrade guide. |
|
This is the only related change needed apache/camel-spring-boot#1672 |
During the spring boot 4 upgrade work I noticed that test-infra module structure can be improved in particular, before each test-infra module split code between src/main (infrastructure services, container implementations) and src/test (service factories, JUnit extensions). This produced two JARs per module: a regular JAR and a test-jar via maven-assembly-plugin.
Now all code lives in src/main. Each module produces a single JAR. The assembly plugin and test-jar goals are removed.
Changes made:
Improvements