KAFKA-18970: Enable client module metadata publication - #22948
Open
lh0156 wants to merge 1 commit into
Open
Conversation
github-actions
Bot
added
triage
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Motivation
KAFKA-18970 tracks the disabled Gradle Module Metadata publication for the clients submodule. The clients publication should provide its .module metadata so Gradle consumers can resolve its published variants and capabilities.
Validation
./gradlew :clients:generateMetadataFileForMavenJavaPublication --no-build-cache --console=plainclients/build/publications/mavenJava/module.jsoncontains theorg.apache.kafka:kafka-clientscomponent and published variants../gradlew --no-daemon :clients:generateMetadataFileForMavenJavaPublication :clients:check --exclude-task test --no-build-cache --console=plaingit diff --checkThe full
:clients:checktest task was also started. It reached the existingKafkaProducerTest.testTopicExpiryInMetadatatest, which remained inKafkaProducer.waitOnMetadatafor over an hour without completing; the run was interrupted after confirming the wait was unrelated to this one-line build configuration change.