cunningt opened a new pull request, #20383:
URL: https://github.com/apache/camel/pull/20383

   # Description
   
   Update Camel to JUnit 6 
   
   - use camel-test-junit6/camel-test-main-junit6/camel-test-spring-junit6 
components
   - use junit6 jupiter dependencies via the JUnit 6 version of the junit-bom
   - change all components, maven plugins, archetypes, test-infra to use JUnit 6
   - change camel-test-junit5 to have a depedencyManagement entry that imports 
the JUnit 5 version of the junit-bom
   - make the necessary API changes (ExtensionContext.Store 
getOrComputeIfAbsent -> computeIfAbsent)
   
   This is a large change that affects almost all tests and I don't know what 
release it makes the most sense to make it in is (we can always convert it to a 
draft PR until ready).     I've tested camel-examples (which currently use 
junit5) and they seem to work okay with this change.
   
   I've given a best effort to run all tests but camel-jms tests and some 
test-infra are failing for me locally without these changes - probably my local 
podman configuration.     I stayed away from changing any junit5 deps in Camel 
JBang that mentioned quarkus because I wasn't sure what the schedule of the 
JUnit5 -> JUnit6 transition is for quarkus.
   
   # Target
   
   - [x ] I checked that the commit is targeting the correct branch (Camel 4 
uses the `main` branch)
   
   # Tracking
   - [x ] If this is a large change, bug fix, or code improvement, I checked 
there is a [JIRA issue](https://issues.apache.org/jira/browse/CAMEL) filed for 
the change (usually before you start working on it).
   
   # Apache Camel coding standards and style
   
   - [x ] I checked that each commit in the pull request has a meaningful 
subject line and body.
   
   - [x ] I have run `mvn clean install -DskipTests` locally from root folder 
and I have committed all auto-generated changes.
   
   


-- 
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]

Reply via email to