-
Notifications
You must be signed in to change notification settings - Fork 56
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to add kafka-connect-http as a Gradle dependency #97
Comments
Hi Matt, Thank you for reporting this. At some point I introduced maven multi-modules in this project, but only the main artifact is accepted as of today in maven central, and I didn't realize. I would need to check with sonatype whether they will accept an artifact that is not named the same as the github repo, so the parent pom can be published. The alternative is kind of unclear to me, because unfortunately there are dependencies across modules that require some build order that I believe wouldn't be possible in a single module. Best regards. |
In the meantime you might want to add github packages repository, all artifacts are published there, so you wouldn't have that issue. |
@castorm thanks, I'll look into that. I'm so far removed from Maven at this point (been working in Gradle for years) that I know nothing about parent POM, Maven best practices, etc. :( |
Tried to get this working, but I think it fails on that kafka-connect-http 0.8.11 depends on kafka-connect-http-parent 0.8.11 where as only kafka-connect-http-parent 0.8.1 seems to be published. |
What would it take to get this fixed? I'm seeing the same thing as @lobbin - the latest kafka-connect-http-parent that has been published to github packages is 0.8.1. So, even after adding gh packages as a maven repository, you still get this error:
|
I am unable to add
kafka-connect-http
as a Gradle dependency as follows:The problem appears to be that
kafka-connect-http-0.8.9.pom
refers to its parent project using a relative path (../pom.xml
) which is not available in the Maven Central repository:The solution is (probably?) to publish the parent POM along with the rest of the artifacts, assuming there's nothing "secret" in it.
Until/unless this is done, the only way to express this dependency is to include the kafka-connect-http.jar in the project and depend on it as a file, which is not ideal for obvious reasons. It does not appear to be possible to avoid this by excluding transitive dependencies.
The raw build output follows.
The text was updated successfully, but these errors were encountered: