oscerd edited a comment on issue #1263: URL: https://github.com/apache/camel-kafka-connector/issues/1263#issuecomment-950328602
> > I don't think you can do in that way, you need to build a tar.gz connector self-containing STS jar in the same folder, so in the plugin path you'll have a directory for S3 Source connector containining all the connector JARs plus the STS jar. In the way you're doing I don't think the folder will be the same. > > My understanding (but it might be wrong) is that it should not need to be in the exact same directory. AFAIU, each connector has its own _top-level_ directory and all JARs from this directory and all its subdirectories should be part of the same classpath. So the separate download as used in the example above should IMHO work, but I never tried this exact combination. In the past, at least locally, I had trouble to make it work when I didn't have the needed JARs in the same exploded directory representing a single connector. That's why I was suggesting this. I'm not sure if it would be the same with Strimzi, but I think the first test I would do would be one based on a local kafka instance to check if the setup works and then eventually move the configuration to Strimzi. > > > I can merge the connector tar gz file and STS JAR locally. However as far as I understand, the artifacts section in the Kafka Connect yaml can only take in urls. And I can't push my locally merged JAR files into the maven repo. > > To download the archive with the connector, it does not need to be in a Maven Central repository. You can prepare your own archive and just put it to any website where it can be downloaded just with a link. You can also build the container image manually => if nothing else that should help to debug the issue (the placement of the JAR 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
