johnpoth commented on issue #3257: URL: https://github.com/apache/camel-k/issues/3257#issuecomment-1119448952
Thank you @casdtodtenhoefer for the detailed report! I created the issue in `spectrum` which is where I think the issue lies. As a workaround you can upload the dependencies manually by using [spectrum](https://github.com/container-tools/spectrum) directly: `spectrum build --base scratch --push-insecure -t localhost:5000/maven_de_org_legacy_legacy_1_0_0_legacy-1_0_0_jar:1.0.0 src/main/resources/legacy.jar` Looks like you've already uploaded the JAR so you will have to also upload the [sha1](https://www.howtohaven.com/system/how-to-hash-file-on-windows.shtml) and [md5](https://www.howtohaven.com/system/how-to-hash-file-on-windows.shtml) files as Maven will look for them and [fail](https://github.com/apache/camel-k/blob/main/pkg/trait/registry.go#L121) if it doesn't find them so something like `spectrum build --base scratch --push-insecure -t localhost:5000/maven_de_org_legacy_legacy_1_0_0_legacy-1_0_0_jar_md5:1.0.0 src/main/resources/legacy.jar_md5` `spectrum build --base scratch --push-insecure -t localhost:5000/maven_de_org_legacy_legacy_1_0_0_legacy-1_0_0_jar_sha1:1.0.0 src/main/resources/legacy.jar_sha1` And you should be all set! You can now reference your legacy jar in your integrations if you enable the registry trait: `kamel run integration-legacy.java -d mvn:de.org.legacy:legacy:1.0.0 -t registry.enabled=true` (we should probably write a doc about this...) Thanks ! -- 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]
