-
Notifications
You must be signed in to change notification settings - Fork 243
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
Build fails for common-config #170
Comments
Any updates on this? This is impeding work on confluentinc/kafka-connect-jdbc#401. |
can some one slove this problem? I have met same issue. |
@RoyalFeng It's not clear what specific error you are getting, but you will need to build Kafka source code before you can build this repo from the master branch.
|
There's nothing broken here, you are trying to build a single module without building its parent modules, and those SNAPSHOTS aren't going to be published in maven central or Confluent's production release maven repository. You should build the full project. If you are just trying to develop downstream projects, you can |
I followed your steps,but still failed. |
@daxiangxiaoyi If you can afford to, please clear your local maven repo or at least move it. mv ~/.m2 ~/.m2.old
git clone https://github.com/confluentinc/kafka.git
cd kafka
./gradlew installAll
git clone https://github.com/confluentinc/common.git
cd common
mvn install The above works for me everytime. |
This works with Here is the failure when running
Do I need to switch the |
You need to use the corresponding Kafka branch for the release. The mapping is documented here. So for example if you want to build the 5.1.x branch you would build the 2.1 branch of Kafka. |
Also, note, the real reason for the failure would be above the |
Thanks @ewencp and @Cricket007 👍 |
so what kafka version is required for 5.3.0-SNAPSHOT? |
2.3-SNAPSHOT. You can find the kafka version, regardless of branch, here https://github.com/confluentinc/common/blob/master/pom.xml#L62 (and it'll also be reported in the error message if you try to build without having the dependency installed). |
And you can find the version being built of the Kafka repo here - https://github.com/confluentinc/kafka/blob/trunk/gradle.properties#L23 |
Using ./gradlew installAll I get the error: |
Try reading the README https://github.com/confluentinc/kafka#installing-the-jars-to-the-local-maven-repository |
I've done everything as supposed, still getting error |
Error suggests you'll need to install this now |
That's correct, this is a very recent change in requirements. I think we're considering just pushing that plugin to maven central so it's easier to get to. |
It will be great, since https://github.com/confluentinc/resolver-maven-plugin is for 5 years ago and trying it didnt help with the issue. |
The version you're getting an error for is 9 days old |
Sorry for the bother, I've cloned the resolver package and tried to mvn it. But I'm still getting the same error: Could you please explain if I had to deploy the resolver package by any special command or get it in any special directory or something?! THNX! |
You'll need to checkout the tag for the version in the error first |
Thanks. EDIT: After finding issues here and there, I finally found out how to build JAR against upcoming 6.0:
Hope this helps. |
If you want to "build latest", for active development, then use master branches |
Add this into your pom file
|
also you can just checkout a release version like git checkout v6.0.1 |
running mvn -pl :common-config package from the parent folder gives the following error:
[ERROR] Failed to execute goal on project common-config: Could not resolve dependencies for project io.confluent:common-config:jar:5.2.0-SNAPSHOT: The following artifacts could not be resolved: io.confluent:common-utils:jar:5.2.0-SNAPSHOT, io.confluent:assembly-plugin-boilerplate:zip:resources:5.2.0-SNAPSHOT: Failure to find io.confluent:common-utils:jar:5.2.0-SNAPSHOT in http://packages.confluent.io/maven/ was cached in the local repository, resolution will not be reattempted until the update interval of confluent has elapsed or updates are forced -> [Help 1]
The text was updated successfully, but these errors were encountered: