You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@kafka.apache.org by "Chad Preisler (Jira)" <ji...@apache.org> on 2023/09/27 23:23:00 UTC

[jira] [Created] (KAFKA-15516) Provide kafka-client library as a proper java Jigsaw module

Chad Preisler created KAFKA-15516:
-------------------------------------

             Summary: Provide kafka-client library as a proper java Jigsaw module
                 Key: KAFKA-15516
                 URL: https://issues.apache.org/jira/browse/KAFKA-15516
             Project: Kafka
          Issue Type: Wish
          Components: clients
    Affects Versions: 3.5.1
            Reporter: Chad Preisler


When a client application depends on the kafka-client library the jlink tool can not be used to generate a custom JDK because the client jar is treated as an automatic module. 

The module-info class can be generated for the JAR files using the jdeps tool or a module-info can be created by hand for each jar. I believe the current structure of the Kafka code can be used as is.

It would be ideal if the Kafka build could properly bundle module-info in the client jar. 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)