davsclaus commented on issue #21: URL: https://github.com/apache/camel-kamelets-examples/issues/21#issuecomment-1562533834
There is a CI build and if it completes, then it published the fix into a ASF snapshot repo http://repository.apache.org/content/groups/snapshots/ The CI job (it runs daily but I kicked it now - it may fail for odd reasons) https://ci-builds.apache.org/job/Camel/job/Camel%20Daily%20Snapshot%20Deploy/job/camel-3.20.x/37/ You can try with the fix with jbang edit this file (is usually in that directory) `.jbang/cache/urls/f20491f9ebc0e16d2fca028eb3d4f03aafdf8cd62b8af1a9d1730bfe382d8165/CamelJBang.java` And change it to use 3.20.5-SNAPSHOT for camel-bom, and camel-jbang-core as shown below: ``` //JAVA 11+ //REPOS mavencentral,apache-snapshot=http://repository.apache.org/content/groups/snapshots/ //DEPS org.apache.camel:camel-bom:${camel.jbang.version:3.20.5-SNASPHOT}@pom //DEPS org.apache.camel:camel-jbang-core:${camel.jbang.version:3.20.5-SNAPSHOT} //DEPS org.apache.camel.kamelets:camel-kamelets:${camel-kamelets.version:3.20.4} ``` Also you can change to use 3.20.5-SNAPSHOT version in maven projects and add that ASF snapshot repo to maven repositories in the pom.xml file http://repository.apache.org/content/groups/snapshots/ The fix is coming in 3.20.6 / 3.21 / 4.0-RC1 etc -- 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: commits-unsubscr...@camel.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
