You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Robin Van Praet (JIRA)" <ji...@apache.org> on 2018/10/08 12:19:00 UTC

[jira] [Created] (KAFKA-7490) Kafka libraries should have a valid module name

Robin Van Praet created KAFKA-7490:
--------------------------------------

             Summary: Kafka libraries should have a valid module name
                 Key: KAFKA-7490
                 URL: https://issues.apache.org/jira/browse/KAFKA-7490
             Project: Kafka
          Issue Type: Improvement
            Reporter: Robin Van Praet


Currently when running an application on Java's module path it is impossible to have kafka as an automatic module.

For example:
{code:java}
<dependency>
   <groupId>org.apache.kafka</groupId>
   <artifactId>kafka_2.12</artifactId>
   <version>2.0.0</version>
</dependency>
{code}
Will result in file kafka_2.12-2.0.0.jar 

The rules for Automatic module naming are:
 * use 'Automatic-Module-Name' value in the Manifest file as value when present
 * convert the jar filename to a module name by stripping the version and converting some characters to a dot.

There is no 'Automatic-Module-Name' value in the Manifest so the jar filename is used. However it will be converted to kafka.2.12 as module name which is not a valid module name.

 

Please provide a 'Automatic-Module-Name' value in the Manifest file for all deliverables



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)