[ https://issues.apache.org/jira/browse/KAFKA-15249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chris Egerton updated KAFKA-15249: ---------------------------------- Fix Version/s: (was: 3.6.0) > Verify Connect test-plugins artifact is published to Maven Central > ------------------------------------------------------------------ > > Key: KAFKA-15249 > URL: https://issues.apache.org/jira/browse/KAFKA-15249 > Project: Kafka > Issue Type: Task > Components: KafkaConnect > Affects Versions: 3.6.0 > Reporter: Chris Egerton > Assignee: Chris Egerton > Priority: Blocker > > In KAFKA-14759 we created a separate {{connect/test-plugins}} module to store > all testing-only Connect plugins and removed those plugins from existing > Connect modules. > These testing-only plugins are intentionally excluded from the project's > release file (which can be generated with {{{}./gradlew releaseTarGz{}}}) > however, some users may still be relying on them for testing environments. > Although we should refrain from distributing these testing-only plugins with > our out-of-the-box distribution of Connect, we should still ensure that > they're available on an opt-in basis to users who would like to continue > using them. This can be accomplished by publishing them to [Maven > Central|https://search.maven.org/], like we do with our other modules. > This will probably happen automatically during the next release (3.6.0) with > no further action required. This ticket is just here as a reminder to verify > that the artifacts are present in the staging Maven repo when release > candidates are published for voting. -- This message was sent by Atlassian Jira (v8.20.10#820010)