[KAFKA-15249] Verify Connect test-plugins artifact is published to Maven Central

• Type: Task
• Status: Resolved
• Priority: Blocker
• Resolution: Done
• Affects Version/s: 3.6.0
• Component/s: connect
• Assignee: Chris Egerton
• Reporter: Chris Egerton
• Created: 25/Jul/23 14:21
• Updated: 15/Oct/23 09:27
• Resolved: 14/Oct/23 19:30

Description

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, 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.

Issue Links

• relates to: KAFKA-14759 Move test-only connectors from connect-runtime to test-specific module