This is an automated email from the ASF dual-hosted git repository.
tcunning pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/camel.git
The following commit(s) were added to refs/heads/main by this push:
new 249ba9113820 Add a section to the migration doc talking about
migrating from the junit5 testing components to junit6
249ba9113820 is described below
commit 249ba91138209e459d0cc4e08d10aa45357a7c0d
Author: Tom Cunningham <[email protected]>
AuthorDate: Thu Mar 19 15:07:33 2026 -0400
Add a section to the migration doc talking about migrating from the junit5
testing components to junit6
---
.../ROOT/pages/camel-4x-upgrade-guide-4_19.adoc | 77 ++++++++++++++++++++++
1 file changed, 77 insertions(+)
diff --git
a/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_19.adoc
b/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_19.adoc
index 78ba86a925e0..2e505a6ecd73 100644
--- a/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_19.adoc
+++ b/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_19.adoc
@@ -273,6 +273,83 @@ The camel-jackson3 component shares a unified DSL with the
camel-jackson compone
The same detection mechanism and combined interface extends to the other
Jackson data formats (avroJackson, protobufJackson, and jacksonXml).
+=== camel-test-junit6, camel-test-main-junit6, camel-test-spring-junit6
+
+camel-test-junit6 was introduced in 4.17.0 - and in 4.19.0 all of the camel
components have moved to using it for testing as part of the upgrade to Spring
Boot 4.0. Migration to JUnit 6 camel-test-* components is optional - the
camel-test-junit5 is still available and is pinned to JUnit 5 use. Migrating
to camel-test-junit6 has the benefit of better alignment with Spring Boot 4.0
(using camel-spring-boot as a runtime). If you are using camel-test-junit5 and
would like to move to cam [...]
+
+Before:
+[source,xml]
+----
+<dependency>
+ <groupId>org.apache.camel</groupId>
+ <artifactId>camel-test-junit5</artifactId>
+ <version>${camel.version}</version>
+ <scope>test</scope>
+</dependency>
+----
+
+After:
+[source,xml]
+----
+<dependency>
+ <groupId>org.apache.camel</groupId>
+ <artifactId>camel-test-junit6</artifactId>
+ <version>${camel.version}</version>
+ <scope>test</scope>
+</dependency>
+----
+
+You will also need to change any imports of classes in
`org.apache.camel.test.junit5.*` to `import org.apache.camel.test.junit6.*`.
+
+Similarly, for camel-test-main-junit5 you would need to change any imports of
classes in `org.apache.camel.test.main.junit5.*` to
`org.apache.camel.test.main.junit6.*`, and the dependency in your pom.xml would
change from:
+
+Before:
+[source,xml]
+----
+<dependency>
+ <groupId>org.apache.camel</groupId>
+ <artifactId>camel-test-main-junit5</artifactId>
+ <version>${camel.version}</version>
+ <scope>test</scope>
+</dependency>
+----
+
+After:
+[source,xml]
+----
+<dependency>
+ <groupId>org.apache.camel</groupId>
+ <artifactId>camel-test-main-junit6</artifactId>
+ <version>${camel.version}</version>
+ <scope>test</scope>
+</dependency>
+----
+
+Finally, for camel-test-spring-junit5 any imports would change from
`org.apache.camel.test.spring.junit5.*` to `import
org.apache.camel.test.spring.junit6.*` and the dependency change would be :
+
+Before:
+[source,xml]
+----
+<dependency>
+ <groupId>org.apache.camel</groupId>
+ <artifactId>camel-test-spring-junit5</artifactId>
+ <version>${camel.version}</version>
+ <scope>test</scope>
+</dependency>
+----
+
+After:
+[source,xml]
+----
+<dependency>
+ <groupId>org.apache.camel</groupId>
+ <artifactId>camel-test-spring-junit6</artifactId>
+ <version>${camel.version}</version>
+ <scope>test</scope>
+</dependency>
+----
+
+
=== camel-jbang
Support for exporting to use Gradle as build tool has been removed (it was
deprecated and not working well)
