[jira] [Updated] (CAMEL-13342) Introduce JUnit 5 testing support
[ https://issues.apache.org/jira/browse/CAMEL-13342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Dettinger updated CAMEL-13342: --- Fix Version/s: 3.0.0.RC4 > Introduce JUnit 5 testing support > - > > Key: CAMEL-13342 > URL: https://issues.apache.org/jira/browse/CAMEL-13342 > Project: Camel > Issue Type: New Feature > Components: camel-test >Reporter: Eric Deandrea >Assignee: Alex Dettinger >Priority: Major > Fix For: 3.0.0, 3.0.0.RC4 > > Attachments: camel-test-cdi-junit5.patch > > > Off-shoot from CAMEL-11807 to allow building support for users to be able to > write Camel tests using JUnit 5. > JUnit 5 versions of the more common test modules have been created: > A camel-test-junit5 dedicated module has been created in CAMEL-13826. > A camel-test-spring-junit5 dedicated module has been created in CAMEL-13965. > A camel-testcontainers-junit5 dedicated module has been created in > CAMEL-14037. > A camel-testcontainers-spring-junit5 dedicated module has been created in > CAMEL-14084. > The attached file camel-test-cdi-junit5.patch stores an experimental > implementation of the camel-test-cdi-junit5 module in case one would be > interested to implement it. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (CAMEL-13342) Introduce JUnit 5 testing support
[ https://issues.apache.org/jira/browse/CAMEL-13342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Dettinger updated CAMEL-13342: --- Description: Off-shoot from CAMEL-11807 to allow building support for users to be able to write Camel tests using JUnit 5. JUnit 5 versions of the more common test modules have been created: A camel-test-junit5 dedicated module has been created in CAMEL-13826. A camel-test-spring-junit5 dedicated module has been created in CAMEL-13965. A camel-testcontainers-junit5 dedicated module has been created in CAMEL-14037. A camel-testcontainers-spring-junit5 dedicated module has been created in CAMEL-14084. The attached file camel-test-cdi-junit5.patch stores an experimental implementation of the camel-test-cdi-junit5 module in case one would be interested to implement it. was: Off-shoot from CAMEL-11807 to allow building support for users to be able to write Camel tests using JUnit 5. JUnit 5 versions of the more common test modules have been created: A camel-test-junit5 dedicated module has been created in CAMEL-13826. A camel-test-spring-junit5 dedicated module has been created in CAMEL-13965. A camel-testcontainers-junit5 dedicated module has been created in CAMEL-14037. A camel-testcontainers-spring-junit5 dedicated module has been created in CAMEL-14084. Migrating flaky tests to JUnit 5 is not recommended until mavensurefire 3 has been released or until open discussions in [the junit team|https://github.com/junit-team/junit5/issues/1558] has converged. The attached file camel-test-cdi-junit5.patch stores an experimental implementation of the camel-test-cdi-junit5 module in case one would be interested to implement it. > Introduce JUnit 5 testing support > - > > Key: CAMEL-13342 > URL: https://issues.apache.org/jira/browse/CAMEL-13342 > Project: Camel > Issue Type: New Feature > Components: camel-test >Reporter: Eric Deandrea >Assignee: Alex Dettinger >Priority: Major > Fix For: 3.0.0 > > Attachments: camel-test-cdi-junit5.patch > > > Off-shoot from CAMEL-11807 to allow building support for users to be able to > write Camel tests using JUnit 5. > JUnit 5 versions of the more common test modules have been created: > A camel-test-junit5 dedicated module has been created in CAMEL-13826. > A camel-test-spring-junit5 dedicated module has been created in CAMEL-13965. > A camel-testcontainers-junit5 dedicated module has been created in > CAMEL-14037. > A camel-testcontainers-spring-junit5 dedicated module has been created in > CAMEL-14084. > The attached file camel-test-cdi-junit5.patch stores an experimental > implementation of the camel-test-cdi-junit5 module in case one would be > interested to implement it. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (CAMEL-13342) Introduce JUnit 5 testing support
[ https://issues.apache.org/jira/browse/CAMEL-13342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Dettinger updated CAMEL-13342: --- Description: Off-shoot from CAMEL-11807 to allow building support for users to be able to write Camel tests using JUnit 5. JUnit 5 versions of the more common test modules have been created: A camel-test-junit5 dedicated module has been created in CAMEL-13826. A camel-test-spring-junit5 dedicated module has been created in CAMEL-13965. A camel-testcontainers-junit5 dedicated module has been created in CAMEL-14037. A camel-testcontainers-spring-junit5 dedicated module has been created in CAMEL-14084. Migrating flaky tests to JUnit 5 is not recommended until mavensurefire 3 has been released or until open discussions in [the junit team|https://github.com/junit-team/junit5/issues/1558] has converged. The attached file camel-test-cdi-junit5.patch stores an experimental implementation of the camel-test-cdi-junit5 module in case one would be interested to implement it. was: Off-shoot from CAMEL-11807 to allow building support for users to be able to write Camel tests using JUnit 5. Some exploratory preparation work have been stored in [a dedicated branch|https://github.com/apache/camel/commits/CAMEL-13342-JUNIT5-EXPLORATORY]. JUnit 5 versions of the more common test modules have been created: A camel-test-junit5 dedicated module has been created in CAMEL-13826. A camel-test-spring-junit5 dedicated module has been created in CAMEL-13965. A camel-testcontainers-junit5 dedicated module has been created in CAMEL-14037. A camel-testcontainers-spring-junit5 dedicated module has been created in CAMEL-14084. Migrating flaky tests to JUnit 5 is not recommended until mavensurefire 3 has been released or until open discussions in [the junit team|https://github.com/junit-team/junit5/issues/1558] has converged. > Introduce JUnit 5 testing support > - > > Key: CAMEL-13342 > URL: https://issues.apache.org/jira/browse/CAMEL-13342 > Project: Camel > Issue Type: New Feature > Components: camel-test >Reporter: Eric Deandrea >Assignee: Alex Dettinger >Priority: Major > Fix For: 3.0.0 > > Attachments: camel-test-cdi-junit5.patch > > > Off-shoot from CAMEL-11807 to allow building support for users to be able to > write Camel tests using JUnit 5. > JUnit 5 versions of the more common test modules have been created: > A camel-test-junit5 dedicated module has been created in CAMEL-13826. > A camel-test-spring-junit5 dedicated module has been created in CAMEL-13965. > A camel-testcontainers-junit5 dedicated module has been created in > CAMEL-14037. > A camel-testcontainers-spring-junit5 dedicated module has been created in > CAMEL-14084. > Migrating flaky tests to JUnit 5 is not recommended until mavensurefire 3 has > been released or until open discussions in [the junit > team|https://github.com/junit-team/junit5/issues/1558] has converged. > The attached file camel-test-cdi-junit5.patch stores an experimental > implementation of the camel-test-cdi-junit5 module in case one would be > interested to implement it. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (CAMEL-13342) Introduce JUnit 5 testing support
[ https://issues.apache.org/jira/browse/CAMEL-13342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Dettinger updated CAMEL-13342: --- Attachment: camel-test-cdi-junit5.patch > Introduce JUnit 5 testing support > - > > Key: CAMEL-13342 > URL: https://issues.apache.org/jira/browse/CAMEL-13342 > Project: Camel > Issue Type: New Feature > Components: camel-test >Reporter: Eric Deandrea >Assignee: Alex Dettinger >Priority: Major > Fix For: 3.0.0 > > Attachments: camel-test-cdi-junit5.patch > > > Off-shoot from CAMEL-11807 to allow building support for users to be able to > write Camel tests using JUnit 5. > Some exploratory preparation work have been stored in [a dedicated > branch|https://github.com/apache/camel/commits/CAMEL-13342-JUNIT5-EXPLORATORY]. > JUnit 5 versions of the more common test modules have been created: > A camel-test-junit5 dedicated module has been created in CAMEL-13826. > A camel-test-spring-junit5 dedicated module has been created in CAMEL-13965. > A camel-testcontainers-junit5 dedicated module has been created in > CAMEL-14037. > A camel-testcontainers-spring-junit5 dedicated module has been created in > CAMEL-14084. > Migrating flaky tests to JUnit 5 is not recommended until mavensurefire 3 has > been released or until open discussions in [the junit > team|https://github.com/junit-team/junit5/issues/1558] has converged. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (CAMEL-13342) Introduce JUnit 5 testing support
[ https://issues.apache.org/jira/browse/CAMEL-13342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Dettinger updated CAMEL-13342: --- Description: Off-shoot from CAMEL-11807 to allow building support for users to be able to write Camel tests using JUnit 5. Some exploratory preparation work have been stored in [a dedicated branch|https://github.com/apache/camel/commits/CAMEL-13342-JUNIT5-EXPLORATORY]. JUnit 5 versions of the more common test modules have been created: A camel-test-junit5 dedicated module has been created in CAMEL-13826. A camel-test-spring-junit5 dedicated module has been created in CAMEL-13965. A camel-testcontainers-junit5 dedicated module has been created in CAMEL-14037. A camel-testcontainers-spring-junit5 dedicated module has been created in CAMEL-14084. Migrating flaky tests to JUnit 5 is not recommended until mavensurefire 3 has been released or until open discussions in [the junit team|https://github.com/junit-team/junit5/issues/1558] has converged. was: Off-shoot from CAMEL-11807 to allow building support for users to be able to write Camel tests using JUnit 5. Some exploratory preparation work have been stored in [a dedicated branch|https://github.com/apache/camel/commits/CAMEL-13342-JUNIT5-EXPLORATORY]. A camel-test-junit5 dedicated module has been created in CAMEL-13826. A camel-test-spring-junit5 dedicated module has been created in CAMEL-13965. A camel-testcontainers-junit5 dedicated module has been created in CAMEL-14037. A camel-testcontainers-spring-junit5 dedicated module has been created in CAMEL-14084. Migrating flaky tests to JUnit 5 is not recommended until mavensurefire 3 has been released or until open discussions in [the junit team|https://github.com/junit-team/junit5/issues/1558] has converged. > Introduce JUnit 5 testing support > - > > Key: CAMEL-13342 > URL: https://issues.apache.org/jira/browse/CAMEL-13342 > Project: Camel > Issue Type: New Feature > Components: camel-test >Reporter: Eric Deandrea >Assignee: Alex Dettinger >Priority: Major > Fix For: 3.0.0 > > > Off-shoot from CAMEL-11807 to allow building support for users to be able to > write Camel tests using JUnit 5. > Some exploratory preparation work have been stored in [a dedicated > branch|https://github.com/apache/camel/commits/CAMEL-13342-JUNIT5-EXPLORATORY]. > JUnit 5 versions of the more common test modules have been created: > A camel-test-junit5 dedicated module has been created in CAMEL-13826. > A camel-test-spring-junit5 dedicated module has been created in CAMEL-13965. > A camel-testcontainers-junit5 dedicated module has been created in > CAMEL-14037. > A camel-testcontainers-spring-junit5 dedicated module has been created in > CAMEL-14084. > Migrating flaky tests to JUnit 5 is not recommended until mavensurefire 3 has > been released or until open discussions in [the junit > team|https://github.com/junit-team/junit5/issues/1558] has converged. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (CAMEL-13342) Introduce JUnit 5 testing support
[ https://issues.apache.org/jira/browse/CAMEL-13342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Dettinger updated CAMEL-13342: --- Description: Off-shoot from CAMEL-11807 to allow building support for users to be able to write Camel tests using JUnit 5. Some exploratory preparation work have been stored in [a dedicated branch|https://github.com/apache/camel/commits/CAMEL-13342-JUNIT5-EXPLORATORY]. A camel-test-junit5 dedicated module has been created in CAMEL-13826. A camel-test-spring-junit5 dedicated module has been created in CAMEL-13965. A camel-testcontainers-junit5 dedicated module has been created in CAMEL-14037. A camel-testcontainers-spring-junit5 dedicated module has been created in CAMEL-14084. Migrating flaky tests to JUnit 5 is not recommended until mavensurefire 3 has been released or until open discussions in [the junit team|https://github.com/junit-team/junit5/issues/1558] has converged. was: Off-shoot from CAMEL-11807 to allow building support for users to be able to write Camel tests using JUnit 5. Some exploratory preparation work have been stored in [a dedicated branch|https://github.com/apache/camel/commits/CAMEL-13342-JUNIT5-EXPLORATORY]. A camel-test-junit5 dedicated module has been created in CAMEL-13826. A camel-test-spring-junit5 dedicated module has been created in CAMEL-13965. A camel-testcontainers-junit5 dedicated module has been created in CAMEL-14037. Other modules will follow: camel-testcontainers-spring-junit5 (prototype [here|https://github.com/apache/camel/commit/d995abb254e892c281494d875cc0dbdab9d26e10]) Migrating flaky tests to JUnit 5 is not recommended until mavensurefire 3 has been released or until open discussions in [the junit team|https://github.com/junit-team/junit5/issues/1558] has converged. > Introduce JUnit 5 testing support > - > > Key: CAMEL-13342 > URL: https://issues.apache.org/jira/browse/CAMEL-13342 > Project: Camel > Issue Type: New Feature > Components: camel-test >Reporter: Eric Deandrea >Assignee: Alex Dettinger >Priority: Major > Fix For: 3.0.0 > > > Off-shoot from CAMEL-11807 to allow building support for users to be able to > write Camel tests using JUnit 5. > Some exploratory preparation work have been stored in [a dedicated > branch|https://github.com/apache/camel/commits/CAMEL-13342-JUNIT5-EXPLORATORY]. > A camel-test-junit5 dedicated module has been created in CAMEL-13826. > A camel-test-spring-junit5 dedicated module has been created in CAMEL-13965. > A camel-testcontainers-junit5 dedicated module has been created in > CAMEL-14037. > A camel-testcontainers-spring-junit5 dedicated module has been created in > CAMEL-14084. > Migrating flaky tests to JUnit 5 is not recommended until mavensurefire 3 has > been released or until open discussions in [the junit > team|https://github.com/junit-team/junit5/issues/1558] has converged. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (CAMEL-13342) Introduce JUnit 5 testing support
[ https://issues.apache.org/jira/browse/CAMEL-13342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Dettinger updated CAMEL-13342: --- Description: Off-shoot from CAMEL-11807 to allow building support for users to be able to write Camel tests using JUnit 5. Some exploratory preparation work have been stored in [a dedicated branch|https://github.com/apache/camel/commits/CAMEL-13342-JUNIT5-EXPLORATORY]. A camel-test-junit5 dedicated module has been created in CAMEL-13826. A camel-test-spring-junit5 dedicated module has been created in CAMEL-13965. A camel-testcontainers-junit5 dedicated module has been created in CAMEL-14037. Other modules will follow: camel-testcontainers-spring-junit5 (prototype [here|https://github.com/apache/camel/commit/d995abb254e892c281494d875cc0dbdab9d26e10]) Migrating flaky tests to JUnit 5 is not recommended until mavensurefire 3 has been released or until open discussions in [the junit team|https://github.com/junit-team/junit5/issues/1558] has converged. was: Off-shoot from CAMEL-11807 to allow building support for users to be able to write Camel tests using JUnit 5. Some exploratory preparation work have been stored in [a dedicated branch|https://github.com/apache/camel/commits/CAMEL-13342-JUNIT5-EXPLORATORY]. A camel-test-junit5 dedicated module has been created in [CAMEL-13826|https://issues.apache.org/jira/projects/CAMEL/issues/CAMEL-13826]. A camel-test-spring-junit5 dedicated module has been created in CAMEL-13965. A camel-testcontainers-junit5 dedicated module has been created in CAMEL-14037. Other modules will follow: camel-testcontainers-spring-junit5 (prototype [here|https://github.com/apache/camel/commit/d995abb254e892c281494d875cc0dbdab9d26e10]) Migrating flaky tests to JUnit 5 is not recommended until mavensurefire 3 has been released or until open discussions in [the junit team|https://github.com/junit-team/junit5/issues/1558] has converged. > Introduce JUnit 5 testing support > - > > Key: CAMEL-13342 > URL: https://issues.apache.org/jira/browse/CAMEL-13342 > Project: Camel > Issue Type: New Feature > Components: camel-test >Reporter: Eric Deandrea >Assignee: Alex Dettinger >Priority: Major > Fix For: 3.0.0 > > > Off-shoot from CAMEL-11807 to allow building support for users to be able to > write Camel tests using JUnit 5. > Some exploratory preparation work have been stored in [a dedicated > branch|https://github.com/apache/camel/commits/CAMEL-13342-JUNIT5-EXPLORATORY]. > A camel-test-junit5 dedicated module has been created in CAMEL-13826. > A camel-test-spring-junit5 dedicated module has been created in CAMEL-13965. > A camel-testcontainers-junit5 dedicated module has been created in > CAMEL-14037. > Other modules will follow: > camel-testcontainers-spring-junit5 (prototype > [here|https://github.com/apache/camel/commit/d995abb254e892c281494d875cc0dbdab9d26e10]) > Migrating flaky tests to JUnit 5 is not recommended until mavensurefire 3 has > been released or until open discussions in [the junit > team|https://github.com/junit-team/junit5/issues/1558] has converged. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (CAMEL-13342) Introduce JUnit 5 testing support
[ https://issues.apache.org/jira/browse/CAMEL-13342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Dettinger updated CAMEL-13342: --- Description: Off-shoot from CAMEL-11807 to allow building support for users to be able to write Camel tests using JUnit 5. Some exploratory preparation work have been stored in [a dedicated branch|https://github.com/apache/camel/commits/CAMEL-13342-JUNIT5-EXPLORATORY]. A camel-test-junit5 dedicated module has been created in [CAMEL-13826|https://issues.apache.org/jira/projects/CAMEL/issues/CAMEL-13826]. A camel-test-spring-junit5 dedicated module has been created in CAMEL-13965. A camel-testcontainers-junit5 dedicated module has been created in CAMEL-14037. Other modules will follow: camel-testcontainers-spring-junit5 (prototype [here|https://github.com/apache/camel/commit/d995abb254e892c281494d875cc0dbdab9d26e10]) Migrating flaky tests to JUnit 5 is not recommended until mavensurefire 3 has been released or until open discussions in [the junit team|https://github.com/junit-team/junit5/issues/1558] has converged. was: Off-shoot from CAMEL-11807 to allow building support for users to be able to write Camel tests using JUnit 5. Some exploratory preparation work have been stored in [a dedicated branch|https://github.com/apache/camel/commits/CAMEL-13342-JUNIT5-EXPLORATORY]. A camel-test-junit5 dedicated module has been created in [CAMEL-13826|https://issues.apache.org/jira/projects/CAMEL/issues/CAMEL-13826]. A camel-test-spring-junit5 dedicated module has been created in [CAMEL-13965|https://issues.apache.org/jira/projects/CAMEL/issues/CAMEL-13965]. A camel-testcontainers-junit5 dedicated module has been created in CAMEL-14037. Other modules will follow: camel-testcontainers-spring-junit5 (prototype [here|https://github.com/apache/camel/commit/d995abb254e892c281494d875cc0dbdab9d26e10]) Migrating flaky tests to JUnit 5 is not recommended until mavensurefire 3 has been released or until open discussions in [the junit team|https://github.com/junit-team/junit5/issues/1558] has converged. > Introduce JUnit 5 testing support > - > > Key: CAMEL-13342 > URL: https://issues.apache.org/jira/browse/CAMEL-13342 > Project: Camel > Issue Type: New Feature > Components: camel-test >Reporter: Eric Deandrea >Assignee: Alex Dettinger >Priority: Major > Fix For: 3.0.0 > > > Off-shoot from CAMEL-11807 to allow building support for users to be able to > write Camel tests using JUnit 5. > Some exploratory preparation work have been stored in [a dedicated > branch|https://github.com/apache/camel/commits/CAMEL-13342-JUNIT5-EXPLORATORY]. > > A camel-test-junit5 dedicated module has been created in > [CAMEL-13826|https://issues.apache.org/jira/projects/CAMEL/issues/CAMEL-13826]. > A camel-test-spring-junit5 dedicated module has been created in CAMEL-13965. > A camel-testcontainers-junit5 dedicated module has been created in > CAMEL-14037. > Other modules will follow: > camel-testcontainers-spring-junit5 (prototype > [here|https://github.com/apache/camel/commit/d995abb254e892c281494d875cc0dbdab9d26e10]) > Migrating flaky tests to JUnit 5 is not recommended until mavensurefire 3 has > been released or until open discussions in [the junit > team|https://github.com/junit-team/junit5/issues/1558] has converged. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (CAMEL-13342) Introduce JUnit 5 testing support
[ https://issues.apache.org/jira/browse/CAMEL-13342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Dettinger updated CAMEL-13342: --- Description: Off-shoot from CAMEL-11807 to allow building support for users to be able to write Camel tests using JUnit 5. Some exploratory preparation work have been stored in [a dedicated branch|https://github.com/apache/camel/commits/CAMEL-13342-JUNIT5-EXPLORATORY]. A camel-test-junit5 dedicated module has been created in [CAMEL-13826|https://issues.apache.org/jira/projects/CAMEL/issues/CAMEL-13826]. A camel-test-spring-junit5 dedicated module has been created in [CAMEL-13965|https://issues.apache.org/jira/projects/CAMEL/issues/CAMEL-13965]. A camel-testcontainers-junit5 dedicated module has been created in CAMEL-14037. Other modules will follow: camel-testcontainers-spring-junit5 (prototype [here|https://github.com/apache/camel/commit/d995abb254e892c281494d875cc0dbdab9d26e10]) Migrating flaky tests to JUnit 5 is not recommended until mavensurefire 3 has been released or until open discussions in [the junit team|https://github.com/junit-team/junit5/issues/1558] has converged. was: Off-shoot from CAMEL-11807 to allow building support for users to be able to write Camel tests using JUnit 5. Some exploratory preparation work have been stored in [a dedicated branch|https://github.com/apache/camel/commits/CAMEL-13342-JUNIT5-EXPLORATORY]. A camel-test-junit5 dedicated module has been created in [CAMEL-13826|https://issues.apache.org/jira/projects/CAMEL/issues/CAMEL-13826]. A camel-test-spring-junit5 dedicated module has been created in [CAMEL-13965|https://issues.apache.org/jira/projects/CAMEL/issues/CAMEL-13965]. A camel-testcontainers-junit5 dedicated module has been created in CAMEL-14037. Other modules will follow: camel-testcontainers-spring-junit5 (prototype [here|https://github.com/apache/camel/commit/d995abb254e892c281494d875cc0dbdab9d26e10]) camel-cdi-test-junit5 ? (prototype [here|https://github.com/apache/camel/commit/cdefa5ca0c3dc1bc040dd89ab23a70da5189ace4]) ... Migrating flaky tests to JUnit 5 is not recommended until mavensurefire 3 has been released or until open discussions in [the junit team|https://github.com/junit-team/junit5/issues/1558] has converged. > Introduce JUnit 5 testing support > - > > Key: CAMEL-13342 > URL: https://issues.apache.org/jira/browse/CAMEL-13342 > Project: Camel > Issue Type: New Feature > Components: camel-test >Reporter: Eric Deandrea >Assignee: Alex Dettinger >Priority: Major > Fix For: 3.0.0 > > > Off-shoot from CAMEL-11807 to allow building support for users to be able to > write Camel tests using JUnit 5. > Some exploratory preparation work have been stored in [a dedicated > branch|https://github.com/apache/camel/commits/CAMEL-13342-JUNIT5-EXPLORATORY]. > > A camel-test-junit5 dedicated module has been created in > [CAMEL-13826|https://issues.apache.org/jira/projects/CAMEL/issues/CAMEL-13826]. > A camel-test-spring-junit5 dedicated module has been created in > [CAMEL-13965|https://issues.apache.org/jira/projects/CAMEL/issues/CAMEL-13965]. > A camel-testcontainers-junit5 dedicated module has been created in > CAMEL-14037. > Other modules will follow: > camel-testcontainers-spring-junit5 (prototype > [here|https://github.com/apache/camel/commit/d995abb254e892c281494d875cc0dbdab9d26e10]) > Migrating flaky tests to JUnit 5 is not recommended until mavensurefire 3 has > been released or until open discussions in [the junit > team|https://github.com/junit-team/junit5/issues/1558] has converged. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (CAMEL-13342) Introduce JUnit 5 testing support
[ https://issues.apache.org/jira/browse/CAMEL-13342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Dettinger updated CAMEL-13342: --- Description: Off-shoot from CAMEL-11807 to allow building support for users to be able to write Camel tests using JUnit 5. Some exploratory preparation work have been stored in [a dedicated branch|https://github.com/apache/camel/commits/CAMEL-13342-JUNIT5-EXPLORATORY]. A camel-test-junit5 dedicated module has been created in [CAMEL-13826|https://issues.apache.org/jira/projects/CAMEL/issues/CAMEL-13826]. A camel-test-spring-junit5 dedicated module has been created in [CAMEL-13965|https://issues.apache.org/jira/projects/CAMEL/issues/CAMEL-13965]. A camel-testcontainers-junit5 dedicated module has been created in CAMEL-14037. Other modules will follow: camel-testcontainers-spring-junit5 (prototype [here|https://github.com/apache/camel/commit/d995abb254e892c281494d875cc0dbdab9d26e10]) camel-cdi-test-junit5 ? (prototype [here|https://github.com/apache/camel/commit/cdefa5ca0c3dc1bc040dd89ab23a70da5189ace4]) ... Migrating flaky tests to JUnit 5 is not recommended until mavensurefire 3 has been released or until open discussions in [the junit team|https://github.com/junit-team/junit5/issues/1558] has converged. was: Off-shoot from CAMEL-11807 to allow building support for users to be able to write Camel tests using JUnit 5. Some exploratory preparation work have been stored in [a dedicated branch|https://github.com/apache/camel/commits/CAMEL-13342-JUNIT5-EXPLORATORY]. A camel-test-junit5 dedicated module has been created in [CAMEL-13826|https://issues.apache.org/jira/projects/CAMEL/issues/CAMEL-13826]. A camel-test-spring-junit5 dedicated module has been created in [CAMEL-13965|https://issues.apache.org/jira/projects/CAMEL/issues/CAMEL-13965]. A camel-testcontainers-junit5 dedicated module has been created in [CAMEL-14037|https://issues.apache.org/jira/browse/CAMEL-14037]. Other modules may follow: camel-testcontainers-spring-junit5 (prototype [here|https://github.com/apache/camel/commit/d995abb254e892c281494d875cc0dbdab9d26e10]) camel-cdi-test-junit5 ? (prototype [here|https://github.com/apache/camel/commit/cdefa5ca0c3dc1bc040dd89ab23a70da5189ace4]) camel-spring-javaconfig-junit5 ? ... Migrating flaky tests to JUnit 5 is not recommended until [mavensurefire 3|https://issues.apache.org/jira/browse/SUREFIRE-1584] has been released or until open discussions in [the junit team|https://github.com/junit-team/junit5/issues/1558] has converged. > Introduce JUnit 5 testing support > - > > Key: CAMEL-13342 > URL: https://issues.apache.org/jira/browse/CAMEL-13342 > Project: Camel > Issue Type: New Feature > Components: camel-test >Reporter: Eric Deandrea >Assignee: Alex Dettinger >Priority: Major > Fix For: 3.0.0 > > > Off-shoot from CAMEL-11807 to allow building support for users to be able to > write Camel tests using JUnit 5. > Some exploratory preparation work have been stored in [a dedicated > branch|https://github.com/apache/camel/commits/CAMEL-13342-JUNIT5-EXPLORATORY]. > > A camel-test-junit5 dedicated module has been created in > [CAMEL-13826|https://issues.apache.org/jira/projects/CAMEL/issues/CAMEL-13826]. > A camel-test-spring-junit5 dedicated module has been created in > [CAMEL-13965|https://issues.apache.org/jira/projects/CAMEL/issues/CAMEL-13965]. > A camel-testcontainers-junit5 dedicated module has been created in > CAMEL-14037. > Other modules will follow: > camel-testcontainers-spring-junit5 (prototype > [here|https://github.com/apache/camel/commit/d995abb254e892c281494d875cc0dbdab9d26e10]) > camel-cdi-test-junit5 ? (prototype > [here|https://github.com/apache/camel/commit/cdefa5ca0c3dc1bc040dd89ab23a70da5189ace4]) > ... > Migrating flaky tests to JUnit 5 is not recommended until mavensurefire 3 has > been released or until open discussions in [the junit > team|https://github.com/junit-team/junit5/issues/1558] has converged. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (CAMEL-13342) Introduce JUnit 5 testing support
[ https://issues.apache.org/jira/browse/CAMEL-13342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Dettinger updated CAMEL-13342: --- Description: Off-shoot from CAMEL-11807 to allow building support for users to be able to write Camel tests using JUnit 5. Some exploratory preparation work have been stored in [a dedicated branch|https://github.com/apache/camel/commits/CAMEL-13342-JUNIT5-EXPLORATORY]. A camel-test-junit5 dedicated module has been created in [CAMEL-13826|https://issues.apache.org/jira/projects/CAMEL/issues/CAMEL-13826]. A camel-test-spring-junit5 dedicated module has been created in [CAMEL-13965|https://issues.apache.org/jira/projects/CAMEL/issues/CAMEL-13965]. A camel-testcontainers-junit5 dedicated module has been created in [CAMEL-14037|https://issues.apache.org/jira/browse/CAMEL-14037]. Other modules may follow: camel-testcontainers-spring-junit5 (prototype [here|https://github.com/apache/camel/commit/d995abb254e892c281494d875cc0dbdab9d26e10]) camel-cdi-test-junit5 ? (prototype [here|https://github.com/apache/camel/commit/cdefa5ca0c3dc1bc040dd89ab23a70da5189ace4]) camel-spring-javaconfig-junit5 ? ... Migrating flaky tests to JUnit 5 is not recommended until [mavensurefire 3|https://issues.apache.org/jira/browse/SUREFIRE-1584] has been released or until open discussions in [the junit team|https://github.com/junit-team/junit5/issues/1558] has converged. was: Off-shoot from CAMEL-11807 to allow building support for users to be able to write Camel tests using JUnit 5. Some exploratory preparation work have been stored in [a dedicated branch|https://github.com/apache/camel/commits/CAMEL-13342-JUNIT5-EXPLORATORY]. A camel-test-junit5 dedicated module has been created in [CAMEL-13826|https://issues.apache.org/jira/projects/CAMEL/issues/CAMEL-13826]. A camel-test-spring-junit5 dedicated module has been created in [CAMEL-13965|https://issues.apache.org/jira/projects/CAMEL/issues/CAMEL-13965]. A camel-testcontainers-junit5 dedicated module has been created in [CAMEL-14037|https://issues.apache.org/jira/browse/CAMEL-14037]. Other modules may follow: camel-testcontainers-spring-junit5 (prototype [here|https://github.com/apache/camel/commit/d995abb254e892c281494d875cc0dbdab9d26e10]) camel-cdi-test-junit5 ? (prototype [here|https://github.com/apache/camel/commit/cdefa5ca0c3dc1bc040dd89ab23a70da5189ace4]) camel-spring-javaconfig-junit5 ? ... Migrating flaky tests to JUnit 5 is not recommended until [mavensurefire 3|https://issues.apache.org/jira/browse/SUREFIRE-1584] has been released or until open discussions at [JUnit 5|https://github.com/junit-team/junit5/issues/1558] has converged. > Introduce JUnit 5 testing support > - > > Key: CAMEL-13342 > URL: https://issues.apache.org/jira/browse/CAMEL-13342 > Project: Camel > Issue Type: New Feature > Components: camel-test >Reporter: Eric Deandrea >Assignee: Alex Dettinger >Priority: Major > Fix For: 3.0.0 > > > Off-shoot from CAMEL-11807 to allow building support for users to be able to > write Camel tests using JUnit 5. > Some exploratory preparation work have been stored in [a dedicated > branch|https://github.com/apache/camel/commits/CAMEL-13342-JUNIT5-EXPLORATORY]. > > A camel-test-junit5 dedicated module has been created in > [CAMEL-13826|https://issues.apache.org/jira/projects/CAMEL/issues/CAMEL-13826]. > A camel-test-spring-junit5 dedicated module has been created in > [CAMEL-13965|https://issues.apache.org/jira/projects/CAMEL/issues/CAMEL-13965]. > A camel-testcontainers-junit5 dedicated module has been created in > [CAMEL-14037|https://issues.apache.org/jira/browse/CAMEL-14037]. > Other modules may follow: > camel-testcontainers-spring-junit5 (prototype > [here|https://github.com/apache/camel/commit/d995abb254e892c281494d875cc0dbdab9d26e10]) > camel-cdi-test-junit5 ? (prototype > [here|https://github.com/apache/camel/commit/cdefa5ca0c3dc1bc040dd89ab23a70da5189ace4]) > camel-spring-javaconfig-junit5 ? > ... > Migrating flaky tests to JUnit 5 is not recommended until [mavensurefire > 3|https://issues.apache.org/jira/browse/SUREFIRE-1584] has been released or > until open discussions in [the junit > team|https://github.com/junit-team/junit5/issues/1558] has converged. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (CAMEL-13342) Introduce JUnit 5 testing support
[ https://issues.apache.org/jira/browse/CAMEL-13342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Dettinger updated CAMEL-13342: --- Description: Off-shoot from CAMEL-11807 to allow building support for users to be able to write Camel tests using JUnit 5. Some exploratory preparation work have been stored in [a dedicated branch|https://github.com/apache/camel/commits/CAMEL-13342-JUNIT5-EXPLORATORY]. A camel-test-junit5 dedicated module has been created in [CAMEL-13826|https://issues.apache.org/jira/projects/CAMEL/issues/CAMEL-13826]. A camel-test-spring-junit5 dedicated module has been created in [CAMEL-13965|https://issues.apache.org/jira/projects/CAMEL/issues/CAMEL-13965]. A camel-testcontainers-junit5 dedicated module has been created in [CAMEL-14037|https://issues.apache.org/jira/browse/CAMEL-14037]. Other modules may follow: camel-testcontainers-spring-junit5 (prototype [here|https://github.com/apache/camel/commit/d995abb254e892c281494d875cc0dbdab9d26e10]) camel-cdi-test-junit5 ? (prototype [here|https://github.com/apache/camel/commit/cdefa5ca0c3dc1bc040dd89ab23a70da5189ace4]) camel-spring-javaconfig-junit5 ? ... Migrating flaky tests to JUnit 5 is not recommended until [mavensurefire 3|https://issues.apache.org/jira/browse/SUREFIRE-1584] has been released or until open discussions at [JUnit 5|https://github.com/junit-team/junit5/issues/1558] has converged. was: Off-shoot from CAMEL-11807 to allow building support for users to be able to write Camel tests using JUnit 5. Some exploratory preparation work have been stored in [a dedicated branch|https://github.com/apache/camel/commits/CAMEL-13342-JUNIT5-EXPLORATORY]. A camel-test-junit5 dedicated module has been created in [CAMEL-13826|https://issues.apache.org/jira/projects/CAMEL/issues/CAMEL-13826]. A camel-test-spring-junit5 dedicated module has been created in [CAMEL-13965|https://issues.apache.org/jira/projects/CAMEL/issues/CAMEL-13965]. A camel-testcontainers-junit5 dedicated module has been created in [CAMEL-14037|https://issues.apache.org/jira/browse/CAMEL-14037]. Other modules may follow: camel-testcontainers-spring-junit5 (prototype [here|https://github.com/apache/camel/commit/d995abb254e892c281494d875cc0dbdab9d26e10]) camel-cdi-test-junit5 ? (prototype [here|https://github.com/apache/camel/commit/cdefa5ca0c3dc1bc040dd89ab23a70da5189ace4]) camel-spring-javaconfig-junit5 ? ... Migrating flaky tests to JUnit 5 is not recommended yet as there are still open discussions at [JUnit 5|https://github.com/junit-team/junit5/issues/1558] as well as Surefire level. > Introduce JUnit 5 testing support > - > > Key: CAMEL-13342 > URL: https://issues.apache.org/jira/browse/CAMEL-13342 > Project: Camel > Issue Type: New Feature > Components: camel-test >Reporter: Eric Deandrea >Assignee: Alex Dettinger >Priority: Major > Fix For: 3.0.0 > > > Off-shoot from CAMEL-11807 to allow building support for users to be able to > write Camel tests using JUnit 5. > Some exploratory preparation work have been stored in [a dedicated > branch|https://github.com/apache/camel/commits/CAMEL-13342-JUNIT5-EXPLORATORY]. > > A camel-test-junit5 dedicated module has been created in > [CAMEL-13826|https://issues.apache.org/jira/projects/CAMEL/issues/CAMEL-13826]. > A camel-test-spring-junit5 dedicated module has been created in > [CAMEL-13965|https://issues.apache.org/jira/projects/CAMEL/issues/CAMEL-13965]. > A camel-testcontainers-junit5 dedicated module has been created in > [CAMEL-14037|https://issues.apache.org/jira/browse/CAMEL-14037]. > Other modules may follow: > camel-testcontainers-spring-junit5 (prototype > [here|https://github.com/apache/camel/commit/d995abb254e892c281494d875cc0dbdab9d26e10]) > camel-cdi-test-junit5 ? (prototype > [here|https://github.com/apache/camel/commit/cdefa5ca0c3dc1bc040dd89ab23a70da5189ace4]) > camel-spring-javaconfig-junit5 ? > ... > Migrating flaky tests to JUnit 5 is not recommended until [mavensurefire > 3|https://issues.apache.org/jira/browse/SUREFIRE-1584] has been released or > until open discussions at [JUnit > 5|https://github.com/junit-team/junit5/issues/1558] has converged. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (CAMEL-13342) Introduce JUnit 5 testing support
[ https://issues.apache.org/jira/browse/CAMEL-13342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Dettinger updated CAMEL-13342: --- Description: Off-shoot from CAMEL-11807 to allow building support for users to be able to write Camel tests using JUnit 5. Some exploratory preparation work have been stored in [a dedicated branch|https://github.com/apache/camel/commits/CAMEL-13342-JUNIT5-EXPLORATORY]. A camel-test-junit5 dedicated module has been created in [CAMEL-13826|https://issues.apache.org/jira/projects/CAMEL/issues/CAMEL-13826]. A camel-test-spring-junit5 dedicated module has been created in [CAMEL-13965|https://issues.apache.org/jira/projects/CAMEL/issues/CAMEL-13965]. A camel-testcontainers-junit5 dedicated module has been created in [CAMEL-14037|https://issues.apache.org/jira/browse/CAMEL-14037]. Other modules may follow: camel-testcontainers-spring-junit5 (prototype [here|https://github.com/apache/camel/commit/d995abb254e892c281494d875cc0dbdab9d26e10]) camel-cdi-test-junit5 ? (prototype [here|https://github.com/apache/camel/commit/cdefa5ca0c3dc1bc040dd89ab23a70da5189ace4]) camel-spring-javaconfig-junit5 ? ... Migrating flaky tests to JUnit 5 is not recommended yet as there are still open discussions at [JUnit 5|https://github.com/junit-team/junit5/issues/1558] as well as Surefire level. was: Off-shoot from CAMEL-11807 to allow building support for users to be able to write Camel tests using JUnit 5. Some exploratory preparation work have been stored in [a dedicated branch|https://github.com/apache/camel/commits/CAMEL-13342-JUNIT5-EXPLORATORY]. A camel-test-junit5 dedicated module has been created in [CAMEL-13826|https://issues.apache.org/jira/projects/CAMEL/issues/CAMEL-13826]. A camel-test-spring-junit5 dedicated module has been created in [CAMEL-13965|https://issues.apache.org/jira/projects/CAMEL/issues/CAMEL-13965]. Other modules may follow: camel-testcontainers-junit5 (prototype [here|https://github.com/apache/camel/commit/e044da13e5e7687730619071cedba84e4170ac7e]) camel-testcontainers-spring-junit5 (prototype [here|https://github.com/apache/camel/commit/d995abb254e892c281494d875cc0dbdab9d26e10]) camel-cdi-test-junit5 ? (prototype [here|https://github.com/apache/camel/commit/cdefa5ca0c3dc1bc040dd89ab23a70da5189ace4]) camel-spring-javaconfig-junit5 ? ... Migrating flaky tests to JUnit 5 is not recommended yet as there are still open discussions at [JUnit 5|https://github.com/junit-team/junit5/issues/1558] as well as Surefire level. > Introduce JUnit 5 testing support > - > > Key: CAMEL-13342 > URL: https://issues.apache.org/jira/browse/CAMEL-13342 > Project: Camel > Issue Type: New Feature > Components: camel-test >Reporter: Eric Deandrea >Assignee: Alex Dettinger >Priority: Major > Fix For: 3.0.0 > > > Off-shoot from CAMEL-11807 to allow building support for users to be able to > write Camel tests using JUnit 5. > Some exploratory preparation work have been stored in [a dedicated > branch|https://github.com/apache/camel/commits/CAMEL-13342-JUNIT5-EXPLORATORY]. > > A camel-test-junit5 dedicated module has been created in > [CAMEL-13826|https://issues.apache.org/jira/projects/CAMEL/issues/CAMEL-13826]. > A camel-test-spring-junit5 dedicated module has been created in > [CAMEL-13965|https://issues.apache.org/jira/projects/CAMEL/issues/CAMEL-13965]. > A camel-testcontainers-junit5 dedicated module has been created in > [CAMEL-14037|https://issues.apache.org/jira/browse/CAMEL-14037]. > Other modules may follow: > camel-testcontainers-spring-junit5 (prototype > [here|https://github.com/apache/camel/commit/d995abb254e892c281494d875cc0dbdab9d26e10]) > camel-cdi-test-junit5 ? (prototype > [here|https://github.com/apache/camel/commit/cdefa5ca0c3dc1bc040dd89ab23a70da5189ace4]) > camel-spring-javaconfig-junit5 ? > ... > Migrating flaky tests to JUnit 5 is not recommended yet as there are still > open discussions at [JUnit > 5|https://github.com/junit-team/junit5/issues/1558] as well as Surefire level. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (CAMEL-13342) Introduce JUnit 5 testing support
[ https://issues.apache.org/jira/browse/CAMEL-13342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Dettinger updated CAMEL-13342: --- Fix Version/s: (was: 3.0.0.RC2) > Introduce JUnit 5 testing support > - > > Key: CAMEL-13342 > URL: https://issues.apache.org/jira/browse/CAMEL-13342 > Project: Camel > Issue Type: New Feature > Components: camel-test >Reporter: Eric Deandrea >Assignee: Alex Dettinger >Priority: Major > Fix For: 3.0.0 > > > Off-shoot from CAMEL-11807 to allow building support for users to be able to > write Camel tests using JUnit 5. > Some exploratory preparation work have been stored in [a dedicated > branch|https://github.com/apache/camel/commits/CAMEL-13342-JUNIT5-EXPLORATORY]. > > A camel-test-junit5 dedicated module has been created in > [CAMEL-13826|https://issues.apache.org/jira/projects/CAMEL/issues/CAMEL-13826]. > A camel-test-spring-junit5 dedicated module has been created in > [CAMEL-13965|https://issues.apache.org/jira/projects/CAMEL/issues/CAMEL-13965]. > Other modules may follow: > camel-testcontainers-junit5 (prototype > [here|https://github.com/apache/camel/commit/e044da13e5e7687730619071cedba84e4170ac7e]) > camel-testcontainers-spring-junit5 (prototype > [here|https://github.com/apache/camel/commit/d995abb254e892c281494d875cc0dbdab9d26e10]) > camel-cdi-test-junit5 ? (prototype > [here|https://github.com/apache/camel/commit/cdefa5ca0c3dc1bc040dd89ab23a70da5189ace4]) > camel-spring-javaconfig-junit5 ? > ... > Migrating flaky tests to JUnit 5 is not recommended yet as there are still > open discussions at [JUnit > 5|https://github.com/junit-team/junit5/issues/1558] as well as Surefire level. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (CAMEL-13342) Introduce JUnit 5 testing support
[ https://issues.apache.org/jira/browse/CAMEL-13342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Dettinger updated CAMEL-13342: --- Description: Off-shoot from CAMEL-11807 to allow building support for users to be able to write Camel tests using JUnit 5. Some exploratory preparation work have been stored in [a dedicated branch|https://github.com/apache/camel/commits/CAMEL-13342-JUNIT5-EXPLORATORY]. A camel-test-junit5 dedicated module has been created in [CAMEL-13826|https://issues.apache.org/jira/projects/CAMEL/issues/CAMEL-13826]. A camel-test-spring-junit5 dedicated module has been created in [CAMEL-13965|https://issues.apache.org/jira/projects/CAMEL/issues/CAMEL-13965]. Other modules may follow: camel-testcontainers-junit5 (prototype [here|https://github.com/apache/camel/commit/e044da13e5e7687730619071cedba84e4170ac7e]) camel-testcontainers-spring-junit5 (prototype [here|https://github.com/apache/camel/commit/d995abb254e892c281494d875cc0dbdab9d26e10]) camel-cdi-test-junit5 ? (prototype [here|https://github.com/apache/camel/commit/cdefa5ca0c3dc1bc040dd89ab23a70da5189ace4]) camel-spring-javaconfig-junit5 ? ... Migrating flaky tests to JUnit 5 is not recommended yet as there are still open discussions at [JUnit 5|https://github.com/junit-team/junit5/issues/1558] as well as Surefire level. was: Off-shoot from CAMEL-11807 to allow building support for users to be able to write Camel tests using JUnit 5. Some exploratory preparation work have been stored in [a dedicated branch|https://github.com/apache/camel/commits/CAMEL-13342-JUNIT5-EXPLORATORY]. A camel-test-junit5 dedicated module has been created in [CAMEL-11826|https://issues.apache.org/jira/projects/CAMEL/issues/CAMEL-13826]. A camel-test-spring-junit5 dedicated module has been created in [CAMEL-11826|https://issues.apache.org/jira/projects/CAMEL/issues/CAMEL-13826]. Other modules may follow: camel-test-spring-junit5 camel-testcontainers-junit5 camel-testcontainers-spring-junit5 ... Migrating flaky tests to JUnit 5 is not recommended yet as there are still open discussions at [JUnit 5|https://github.com/junit-team/junit5/issues/1558] as well as Surefire level. > Introduce JUnit 5 testing support > - > > Key: CAMEL-13342 > URL: https://issues.apache.org/jira/browse/CAMEL-13342 > Project: Camel > Issue Type: New Feature > Components: camel-test >Reporter: Eric Deandrea >Assignee: Alex Dettinger >Priority: Major > Fix For: 3.0.0, 3.0.0.RC2 > > > Off-shoot from CAMEL-11807 to allow building support for users to be able to > write Camel tests using JUnit 5. > Some exploratory preparation work have been stored in [a dedicated > branch|https://github.com/apache/camel/commits/CAMEL-13342-JUNIT5-EXPLORATORY]. > > A camel-test-junit5 dedicated module has been created in > [CAMEL-13826|https://issues.apache.org/jira/projects/CAMEL/issues/CAMEL-13826]. > A camel-test-spring-junit5 dedicated module has been created in > [CAMEL-13965|https://issues.apache.org/jira/projects/CAMEL/issues/CAMEL-13965]. > Other modules may follow: > camel-testcontainers-junit5 (prototype > [here|https://github.com/apache/camel/commit/e044da13e5e7687730619071cedba84e4170ac7e]) > camel-testcontainers-spring-junit5 (prototype > [here|https://github.com/apache/camel/commit/d995abb254e892c281494d875cc0dbdab9d26e10]) > camel-cdi-test-junit5 ? (prototype > [here|https://github.com/apache/camel/commit/cdefa5ca0c3dc1bc040dd89ab23a70da5189ace4]) > camel-spring-javaconfig-junit5 ? > ... > Migrating flaky tests to JUnit 5 is not recommended yet as there are still > open discussions at [JUnit > 5|https://github.com/junit-team/junit5/issues/1558] as well as Surefire level. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (CAMEL-13342) Introduce JUnit 5 testing support
[ https://issues.apache.org/jira/browse/CAMEL-13342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Dettinger updated CAMEL-13342: --- Description: Off-shoot from CAMEL-11807 to allow building support for users to be able to write Camel tests using JUnit 5. Some exploratory preparation work have been stored in [a dedicated branch|https://github.com/apache/camel/commits/CAMEL-13342-JUNIT5-EXPLORATORY]. A camel-test-junit5 dedicated module has been created in [CAMEL-11826|https://issues.apache.org/jira/projects/CAMEL/issues/CAMEL-13826]. A camel-test-spring-junit5 dedicated module has been created in [CAMEL-11826|https://issues.apache.org/jira/projects/CAMEL/issues/CAMEL-13826]. Other modules may follow: camel-test-spring-junit5 camel-testcontainers-junit5 camel-testcontainers-spring-junit5 ... Migrating flaky tests to JUnit 5 is not recommended yet as there are still open discussions at [JUnit 5|https://github.com/junit-team/junit5/issues/1558] as well as Surefire level. was: Off-shoot from CAMEL-11807 to allow building support for users to be able to write Camel tests using JUnit 5. Some exploratory preparation work have been stored in [a dedicated branch|https://github.com/apache/camel/commits/CAMEL-13342-JUNIT5-EXPLORATORY]. A camel-test-junit5 dedicated module has been created in [CAMEL-11826|https://issues.apache.org/jira/projects/CAMEL/issues/CAMEL-13826]. Other modules may follow: camel-test-spring-junit5 camel-testcontainers-junit5 camel-testcontainers-spring-junit5 ... Migrating flaky tests to JUnit 5 is not recommended yet as there are still open discussions at [JUnit 5|https://github.com/junit-team/junit5/issues/1558] as well as Surefire level. > Introduce JUnit 5 testing support > - > > Key: CAMEL-13342 > URL: https://issues.apache.org/jira/browse/CAMEL-13342 > Project: Camel > Issue Type: New Feature > Components: camel-test >Reporter: Eric Deandrea >Assignee: Alex Dettinger >Priority: Major > Fix For: 3.0.0, 3.0.0.RC2 > > > Off-shoot from CAMEL-11807 to allow building support for users to be able to > write Camel tests using JUnit 5. > Some exploratory preparation work have been stored in [a dedicated > branch|https://github.com/apache/camel/commits/CAMEL-13342-JUNIT5-EXPLORATORY]. > > A camel-test-junit5 dedicated module has been created in > [CAMEL-11826|https://issues.apache.org/jira/projects/CAMEL/issues/CAMEL-13826]. > A camel-test-spring-junit5 dedicated module has been created in > [CAMEL-11826|https://issues.apache.org/jira/projects/CAMEL/issues/CAMEL-13826]. > Other modules may follow: > camel-test-spring-junit5 > camel-testcontainers-junit5 > camel-testcontainers-spring-junit5 > ... > Migrating flaky tests to JUnit 5 is not recommended yet as there are still > open discussions at [JUnit > 5|https://github.com/junit-team/junit5/issues/1558] as well as Surefire level. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (CAMEL-13342) Introduce JUnit 5 testing support
[ https://issues.apache.org/jira/browse/CAMEL-13342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Dettinger updated CAMEL-13342: --- Description: Off-shoot from CAMEL-11807 to allow building support for users to be able to write Camel tests using JUnit 5. Some exploratory preparation work have been stored in [a dedicated branch|https://github.com/apache/camel/commits/CAMEL-13342-JUNIT5-EXPLORATORY]. A camel-test-junit5 dedicated module has been created in [CAMEL-11826|https://issues.apache.org/jira/projects/CAMEL/issues/CAMEL-13826]. Other modules may follow: camel-test-spring-junit5 camel-testcontainers-junit5 camel-testcontainers-spring-junit5 ... Migrating flaky tests to JUnit 5 is not recommended yet as there are still open discussions at [JUnit 5|https://github.com/junit-team/junit5/issues/1558] as well as Surefire level. was: Off-shoot from CAMEL-11807 to allow building support for users to be able to write Camel tests using JUnit 5. Some exploratory preparation work have been stored in [a dedicated branch|https://github.com/apache/camel/commits/CAMEL-13342-JUNIT5-EXPLORATORY]. A camel-test-junit5 dedicated module has been created in [CAMEL-11826|https://issues.apache.org/jira/projects/CAMEL/issues/CAMEL-13826]. Other modules may follow: camel-test-spring-junit5 camel-test-spring-boot-junit5 camel-testcontainers-junit5 camel-testcontainers-spring-junit5 ... Migrating flaky tests to JUnit 5 is not recommended yet as there are still open discussions at [JUnit 5|https://github.com/junit-team/junit5/issues/1558] as well as [Surefire|https://issues.apache.org/jira/browse/SUREFIRE-1584] level. > Introduce JUnit 5 testing support > - > > Key: CAMEL-13342 > URL: https://issues.apache.org/jira/browse/CAMEL-13342 > Project: Camel > Issue Type: New Feature > Components: camel-test >Reporter: Eric Deandrea >Assignee: Alex Dettinger >Priority: Major > Fix For: 3.0.0, 3.0.0.RC2 > > > Off-shoot from CAMEL-11807 to allow building support for users to be able to > write Camel tests using JUnit 5. > Some exploratory preparation work have been stored in [a dedicated > branch|https://github.com/apache/camel/commits/CAMEL-13342-JUNIT5-EXPLORATORY]. > A camel-test-junit5 dedicated module has been created in > [CAMEL-11826|https://issues.apache.org/jira/projects/CAMEL/issues/CAMEL-13826]. > Other modules may follow: > camel-test-spring-junit5 > camel-testcontainers-junit5 > camel-testcontainers-spring-junit5 > ... > Migrating flaky tests to JUnit 5 is not recommended yet as there are still > open discussions at [JUnit > 5|https://github.com/junit-team/junit5/issues/1558] as well as Surefire level. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (CAMEL-13342) Introduce JUnit 5 testing support
[ https://issues.apache.org/jira/browse/CAMEL-13342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Dettinger updated CAMEL-13342: --- Description: Off-shoot from CAMEL-11807 to allow building support for users to be able to write Camel tests using JUnit 5. Some exploratory preparation work have been stored in [a dedicated branch|https://github.com/apache/camel/commits/CAMEL-13342-JUNIT5-EXPLORATORY]. A camel-test-junit5 dedicated module has been created in [CAMEL-11826|https://issues.apache.org/jira/projects/CAMEL/issues/CAMEL-13826]. Other modules may follow: camel-test-spring-junit5 camel-test-spring-boot-junit5 camel-testcontainers-junit5 camel-testcontainers-spring-junit5 ... Migrating flaky tests to JUnit 5 is not recommended yet as there are still open discussions at [JUnit 5|https://github.com/junit-team/junit5/issues/1558] as well as [Surefire|https://issues.apache.org/jira/browse/SUREFIRE-1584] level. was: Off-shoot from CAMEL-11807 to allow building support for users to be able to write Camel tests using JUnit 5. Some exploratory preparation work have been stored in [a dedicated branch|https://github.com/apache/camel/commits/CAMEL-13342-JUNIT5-EXPLORATORY]. A camel-test-junit5 dedicated module has been created in [CAMEL-11826|https://issues.apache.org/jira/projects/CAMEL/issues/CAMEL-13826]. Other modules may follow: camel-test-spring-junit5 camel-test-spring-boot-junit5 camel-testcontainers-junit5 camel-testcontainers-spring-junit5 ... Migrating flaky tests to JUnit 5 is not recommended yet as there are still open discussions at [JUnit 5|https://github.com/junit-team/junit5/issues/1558] as well as Surefire level. > Introduce JUnit 5 testing support > - > > Key: CAMEL-13342 > URL: https://issues.apache.org/jira/browse/CAMEL-13342 > Project: Camel > Issue Type: New Feature > Components: camel-test >Reporter: Eric Deandrea >Assignee: Alex Dettinger >Priority: Major > Fix For: 3.0.0, 3.0.0.RC2 > > > Off-shoot from CAMEL-11807 to allow building support for users to be able to > write Camel tests using JUnit 5. > Some exploratory preparation work have been stored in [a dedicated > branch|https://github.com/apache/camel/commits/CAMEL-13342-JUNIT5-EXPLORATORY]. > A camel-test-junit5 dedicated module has been created in > [CAMEL-11826|https://issues.apache.org/jira/projects/CAMEL/issues/CAMEL-13826]. > Other modules may follow: > camel-test-spring-junit5 > camel-test-spring-boot-junit5 > camel-testcontainers-junit5 > camel-testcontainers-spring-junit5 > ... > Migrating flaky tests to JUnit 5 is not recommended yet as there are still > open discussions at [JUnit > 5|https://github.com/junit-team/junit5/issues/1558] as well as > [Surefire|https://issues.apache.org/jira/browse/SUREFIRE-1584] level. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (CAMEL-13342) Introduce JUnit 5 testing support
[ https://issues.apache.org/jira/browse/CAMEL-13342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Dettinger updated CAMEL-13342: --- Description: Off-shoot from CAMEL-11807 to allow building support for users to be able to write Camel tests using JUnit 5. Some exploratory preparation work have been stored in [a dedicated branch|https://github.com/apache/camel/commits/CAMEL-13342-JUNIT5-EXPLORATORY]. A camel-test-junit5 dedicated module has been created in [CAMEL-11826|https://issues.apache.org/jira/projects/CAMEL/issues/CAMEL-13826]. Other modules may follow: camel-test-spring-junit5 camel-test-spring-boot-junit5 camel-testcontainers-junit5 camel-testcontainers-spring-junit5 ... Migrating flaky tests to JUnit 5 is not recommended yet as there are still open discussions at [JUnit 5|https://github.com/junit-team/junit5/issues/1558] as well as Surefire level. was: Off-shoot from CAMEL-11807 to allow building support for users to be able to write Camel tests using JUnit 5. Some exploratory preparation work have been stored in [a dedicated branch|https://github.com/apache/camel/commits/CAMEL-13342-JUNIT5-EXPLORATORY]. A camel-test-junit5 dedicated module has been created in [CAMEL-11826|https://issues.apache.org/jira/projects/CAMEL/issues/CAMEL-13826]. Other modules may follow: camel-test-spring-junit5 camel-test-spring-boot-junit5 camel-testcontainers-junit5 camel-testcontainers-spring-junit5 ... > Introduce JUnit 5 testing support > - > > Key: CAMEL-13342 > URL: https://issues.apache.org/jira/browse/CAMEL-13342 > Project: Camel > Issue Type: New Feature > Components: camel-test >Reporter: Eric Deandrea >Assignee: Alex Dettinger >Priority: Major > Fix For: 3.0.0, 3.0.0.RC2 > > > Off-shoot from CAMEL-11807 to allow building support for users to be able to > write Camel tests using JUnit 5. > Some exploratory preparation work have been stored in [a dedicated > branch|https://github.com/apache/camel/commits/CAMEL-13342-JUNIT5-EXPLORATORY]. > A camel-test-junit5 dedicated module has been created in > [CAMEL-11826|https://issues.apache.org/jira/projects/CAMEL/issues/CAMEL-13826]. > Other modules may follow: > camel-test-spring-junit5 > camel-test-spring-boot-junit5 > camel-testcontainers-junit5 > camel-testcontainers-spring-junit5 > ... > Migrating flaky tests to JUnit 5 is not recommended yet as there are still > open discussions at [JUnit > 5|https://github.com/junit-team/junit5/issues/1558] as well as Surefire level. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (CAMEL-13342) Introduce JUnit 5 testing support
[ https://issues.apache.org/jira/browse/CAMEL-13342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Dettinger updated CAMEL-13342: --- Description: Off-shoot from CAMEL-11807 to allow building support for users to be able to write Camel tests using JUnit 5. Some exploratory preparation work have been stored in [a dedicated branch|https://github.com/apache/camel/commits/CAMEL-13342-JUNIT5-EXPLORATORY]. A camel-test-junit5 dedicated module has been created in [CAMEL-11826|https://issues.apache.org/jira/projects/CAMEL/issues/CAMEL-13826]. Other modules may follow: camel-test-spring-junit5 camel-test-spring-boot-junit5 camel-testcontainers-junit5 camel-testcontainers-spring-junit5 ... was: Off-shoot from CAMEL-11807 to allow building support for users to be able to write Camel tests using JUnit 5. Some exploratory preparation work have been stored in [a dedicated branch|https://github.com/apache/camel/commits/CAMEL-13342-JUNIT5-EXPLORATORY]. The current step is to create a camel-test-junit5 dedicated module. > Introduce JUnit 5 testing support > - > > Key: CAMEL-13342 > URL: https://issues.apache.org/jira/browse/CAMEL-13342 > Project: Camel > Issue Type: New Feature > Components: camel-test >Reporter: Eric Deandrea >Assignee: Alex Dettinger >Priority: Major > Fix For: 3.0.0, 3.0.0.RC2 > > > Off-shoot from CAMEL-11807 to allow building support for users to be able to > write Camel tests using JUnit 5. > Some exploratory preparation work have been stored in [a dedicated > branch|https://github.com/apache/camel/commits/CAMEL-13342-JUNIT5-EXPLORATORY]. > A camel-test-junit5 dedicated module has been created in > [CAMEL-11826|https://issues.apache.org/jira/projects/CAMEL/issues/CAMEL-13826]. > Other modules may follow: > camel-test-spring-junit5 > camel-test-spring-boot-junit5 > camel-testcontainers-junit5 > camel-testcontainers-spring-junit5 > ... -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (CAMEL-13342) Introduce JUnit 5 testing support
[ https://issues.apache.org/jira/browse/CAMEL-13342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gregor Zurowski updated CAMEL-13342: Fix Version/s: (was: 3.0.0.RC1) 3.0.0.RC2 > Introduce JUnit 5 testing support > - > > Key: CAMEL-13342 > URL: https://issues.apache.org/jira/browse/CAMEL-13342 > Project: Camel > Issue Type: New Feature > Components: camel-test >Reporter: Eric Deandrea >Assignee: Alex Dettinger >Priority: Major > Fix For: 3.0.0, 3.0.0.RC2 > > > Off-shoot from CAMEL-11807 to allow building support for users to be able to > write Camel tests using JUnit 5. > Some exploratory preparation work have been stored in [a dedicated > branch|https://github.com/apache/camel/commits/CAMEL-13342-JUNIT5-EXPLORATORY]. > > The current step is to create a camel-test-junit5 dedicated module. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (CAMEL-13342) Introduce JUnit 5 testing support
[ https://issues.apache.org/jira/browse/CAMEL-13342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-13342: Fix Version/s: 3.0.0.M5 > Introduce JUnit 5 testing support > - > > Key: CAMEL-13342 > URL: https://issues.apache.org/jira/browse/CAMEL-13342 > Project: Camel > Issue Type: New Feature > Components: camel-test >Reporter: Eric Deandrea >Assignee: Alex Dettinger >Priority: Major > Fix For: 3.0.0, 3.0.0.M5 > > > Off-shoot from CAMEL-11807 to allow building support for users to be able to > write Camel tests using JUnit 5. > Some exploratory preparation work have been stored in [a dedicated > branch|https://github.com/apache/camel/commits/CAMEL-13342-JUNIT5-EXPLORATORY]. > > The current step is to create a camel-test-junit5 dedicated module. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Updated] (CAMEL-13342) Introduce JUnit 5 testing support
[ https://issues.apache.org/jira/browse/CAMEL-13342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Dettinger updated CAMEL-13342: --- Description: Off-shoot from CAMEL-11807 to allow building support for users to be able to write Camel tests using JUnit 5. Some exploratory preparation work have been stored in [a dedicated branch|https://github.com/apache/camel/commits/CAMEL-13342-JUNIT5-EXPLORATORY]. The current step is to create a camel-test-junit5 dedicated module. was: Off-shoot from CAMEL-11807 to allow building support for users to be able to write Camel tests using JUnit 5. Exploratory preparation work happens in [a dedicated branch|https://github.com/apache/camel/commits/CAMEL-13342-JUNIT5-EXPLORATORY]. > Introduce JUnit 5 testing support > - > > Key: CAMEL-13342 > URL: https://issues.apache.org/jira/browse/CAMEL-13342 > Project: Camel > Issue Type: New Feature > Components: camel-test >Reporter: Eric Deandrea >Assignee: Alex Dettinger >Priority: Major > Fix For: 3.0.0 > > > Off-shoot from CAMEL-11807 to allow building support for users to be able to > write Camel tests using JUnit 5. > Some exploratory preparation work have been stored in [a dedicated > branch|https://github.com/apache/camel/commits/CAMEL-13342-JUNIT5-EXPLORATORY]. > > The current step is to create a camel-test-junit5 dedicated module. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Updated] (CAMEL-13342) Introduce JUnit 5 testing support
[ https://issues.apache.org/jira/browse/CAMEL-13342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-13342: Fix Version/s: 3.0.0 > Introduce JUnit 5 testing support > - > > Key: CAMEL-13342 > URL: https://issues.apache.org/jira/browse/CAMEL-13342 > Project: Camel > Issue Type: New Feature > Components: camel-test >Reporter: Eric Deandrea >Assignee: Alex Dettinger >Priority: Minor > Fix For: 3.0.0 > > > Off-shoot from CAMEL-11807 to allow building support for users to be able to > write Camel tests using JUnit 5. > > Exploratory preparation work happens in [a dedicated > branch|https://github.com/apache/camel/commits/CAMEL-13342-JUNIT5-EXPLORATORY]. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Updated] (CAMEL-13342) Introduce JUnit 5 testing support
[ https://issues.apache.org/jira/browse/CAMEL-13342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-13342: Priority: Major (was: Minor) > Introduce JUnit 5 testing support > - > > Key: CAMEL-13342 > URL: https://issues.apache.org/jira/browse/CAMEL-13342 > Project: Camel > Issue Type: New Feature > Components: camel-test >Reporter: Eric Deandrea >Assignee: Alex Dettinger >Priority: Major > Fix For: 3.0.0 > > > Off-shoot from CAMEL-11807 to allow building support for users to be able to > write Camel tests using JUnit 5. > > Exploratory preparation work happens in [a dedicated > branch|https://github.com/apache/camel/commits/CAMEL-13342-JUNIT5-EXPLORATORY]. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Updated] (CAMEL-13342) Introduce JUnit 5 testing support
[ https://issues.apache.org/jira/browse/CAMEL-13342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Dettinger updated CAMEL-13342: --- Description: Off-shoot from CAMEL-11807 to allow building support for users to be able to write Camel tests using JUnit 5. Exploratory preparation work happens in [a dedicated branch|https://github.com/apache/camel/commits/CAMEL-13342-JUNIT5-EXPLORATORY]. was:Off-shoot from CAMEL-11807 to allow building support for users to be able to write Camel tests using JUnit 5. > Introduce JUnit 5 testing support > - > > Key: CAMEL-13342 > URL: https://issues.apache.org/jira/browse/CAMEL-13342 > Project: Camel > Issue Type: New Feature > Components: camel-test >Reporter: Eric Deandrea >Assignee: Alex Dettinger >Priority: Minor > > Off-shoot from CAMEL-11807 to allow building support for users to be able to > write Camel tests using JUnit 5. > > Exploratory preparation work happens in [a dedicated > branch|https://github.com/apache/camel/commits/CAMEL-13342-JUNIT5-EXPLORATORY]. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
