Croway opened a new pull request, #21577: URL: https://github.com/apache/camel/pull/21577
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: - Moved src/test/java -> src/main/java in 60 test-infra modules - Removed assembly plugin from test-infra/pom.xml - Removed test-jar plugin from camel-test-infra-parent/pom.xml - Changed JUnit and testcontainers dependency scopes from test to compile in the parent POM (safe because consumers always use test-infra in <scope>test</scope>) - Removed ~113 <type>test-jar</type> dependency entries from component POMs - Removed ~60 duplicate camel-test-infra-common and redundant testcontainers entries from test-infra module POMs Improvements - 1 dependency instead of 2 per test-infra module in every consumer - ~170 fewer dependency declarations across the codebase - Simpler build, no assembly plugin, no test-jar packaging - camel-jbang infra continues to work unchanged (it already downloaded the regular JAR) - No behavioral changes, all classes remain in the same packages, all tests pass -- 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]
