[KAFKA-16359] kafka-clients-3.7.0.jar published to Maven Central is defective

• Type: Bug
• Status: Resolved
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 3.7.0
• Fix Version/s: 3.8.0, 3.7.1
• Component/s: clients
• Assignee: Apoorv Mittal
• Reporter: Jeremy Norris
• Created: 11/Mar/24 12:43
• Updated: 04/Apr/24 09:56
• Resolved: 04/Apr/24 09:56

Description

The kafka-clients-3.7.0.jar that has been published to Maven Central is defective: it's META-INF/MANIFEST.MF bogusly include a Class-Path element:

Manifest-Version: 1.0
Class-Path: zstd-jni-1.5.5-6.jar lz4-java-1.8.0.jar snappy-java-1.1.10
.5.jar slf4j-api-1.7.36.jar

This bogus Class-Path element leads to compiler warnings for projects that utilize it as a dependency:

[WARNING] [path] bad path element ".../.m2/repository/org/apache/kafka/kafka-clients/3.7.0/zstd-jni-1.5.5-6.jar": no such file or directory
[WARNING] [path] bad path element ".../.m2/repository/org/apache/kafka/kafka-clients/3.7.0/lz4-java-1.8.0.jar": no such file or directory
[WARNING] [path] bad path element ".../.m2/repository/org/apache/kafka/kafka-clients/3.7.0/snappy-java-1.1.10.5.jar": no such file or directory
[WARNING] [path] bad path element ".../.m2/repository/org/apache/kafka/kafka-clients/3.7.0/slf4j-api-1.7.36.jar": no such file or directory

Either the kafka-clients-3.7.0.jar needs to be respun and published without the bogus Class-Path element in it's META-INF/MANIFEST.MF or a new release should be published that corrects this defect.

Issue Links

• duplicates: KAFKA-16357 Kafka Client JAR manifest breaks javac linting
• links to: GitHub Pull Request #15532