[
https://issues.apache.org/jira/browse/CAMEL-25465?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18125075#comment-18125075
]
Federico Mariani commented on CAMEL-25465:
------------------------------------------
PR: https://github.com/apache/camel-spring-boot/pull/2024
> camel-spring-boot - Speed up and harden the starter integration test harness
> ----------------------------------------------------------------------------
>
> Key: CAMEL-25465
> URL: https://issues.apache.org/jira/browse/CAMEL-25465
> Project: Camel
> Issue Type: Improvement
> Components: camel-spring-boot
> Reporter: Federico Mariani
> Assignee: Federico Mariani
> Priority: Major
>
> The starter integration tests in tests/camel-itest-spring-boot run two nested
> Maven JVMs per test (archetype:generate, then compile +
> dependency:build-classpath), which is about three quarters of each test's
> time. The dependency version mismatch check can also never fail, and the
> harness puts the whole Maven runtime (maven-core: guava, guice, asm...) on
> the parent classloader of the application under test, shadowing the starter's
> own versions.
> Improvements:
> * generate the archetype project once per build (file-locked template under
> target/) and copy it per test
> * nested Maven runs share one runner: -nsu, 1 GB heap, output captured on
> failure
> * version mismatch check anchored on the local repository, hard failure for
> org.apache.camel and org.apache.camel.springboot artifacts, warnings only for
> other groups differing in major.minor
> * maven-core replaced by maven-model
> * lazy archetype config, class-level store, fat-jar IT asserts all routes,
> small cleanups
> A single IT goes from about 6s to 3s.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
