[
https://issues.apache.org/jira/browse/CAMEL-22750?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-22750:
--------------------------------
Fix Version/s: 4.x
> junit-bom import : junit 5 to junit 6 migration
> -----------------------------------------------
>
> Key: CAMEL-22750
> URL: https://issues.apache.org/jira/browse/CAMEL-22750
> Project: Camel
> Issue Type: Task
> Components: build system, tests
> Reporter: Thomas Cunningham
> Priority: Major
> Fix For: 4.x
>
>
> In camel-parent, there is a dependencyManagement entry in which the junit-bom
> is imported, of version ${junit-jupiter-version}
> [https://github.com/apache/camel/blob/main/parent/pom.xml#L3125-L3131]
> I'm not sure what the migration plans are for the camel junit 5 to junit 6
> migration, but the bom import means that the junit5 versions of the jupiter
> artifacts bleed in even if a component tries to use camel-test-junit6.
> One solution to this would be to possibly add a profile to activate junit6
> support and import the ${junit6-jupiter-version} of junit-bom when the junit6
> profile is active - or we can migrate all the components to junit6 all at
> once.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
