Build: Update Camel version to 4.19.0-SNAPSHOT#157
Conversation
Updated the parent and dependency versions from 4.18.0-SNAPSHOT to 4.19.0-SNAPSHOT to align with the current development cycle and fix build failures caused by missing artifacts in the Apache Snapshot repository.
|
I think the errors in the log being hit are a product of the JUnit 6 changes in camel. If you change the references to camel-test-junit5 -> camel-test-junit6 they may go away. |
|
Thanks for the heads-up.That makes perfect sense. My local build was likely passing because it was using cached camel-test-junit5 artifacts from my .m2 directory, but I see why the CI is failing now that the 4.19.0-SNAPSHOT cycle has moved to JUnit 6. I will update all references from camel-test-junit5 to camel-test-junit6 across the examples and push the changes shortly. Appreciate the guidance. |
Use JUnit6 for camel-test
|
Aligned with 4.19.0-SNAPSHOT and moved to camel-test-junit6. Big thanks to @cunningt for creating the PR and assisting with the change. |
Problem:
The current main branch of camel-examples is pointing to 4.18.0-SNAPSHOT. Since Camel 4.18.0 has been officially released, these snapshot artifacts have been removed from the Apache Snapshot repository. This causes build failures (Missing Artifact errors) for any new developer cloning the repository.
Solution:
This PR aligns the camel-examples repository with the current main development branch of Apache Camel by bumping the version to 4.19.0-SNAPSHOT.
Changes:
Updated the parent and dependency versions in the root pom.xml and all sub-modules.
Updated version references in README files and sample log outputs to ensure documentation consistency.
Testing:
Verified the build passes from the root directory using mvn clean install -DskipTests -U.
Confirmed that the 4.19.0-SNAPSHOT artifacts are correctly resolved from the Apache Snapshot repository.
Applied mvn spotless:apply to maintain project code style.