Add proper module name in Manifest

Open Beginner friendly

#731 opened on Apr 1, 2026 16 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty: 2/5
Estimated time: 1-3 hours
Newbie friendliness: 65/100

Issue type: Feature
Clarity: Mostly clear
Activity status: Quiet
Tech stack: java
Domain: build-system

Research direction

Start with the Maven build configuration that creates the library JAR and compare its generated manifest with the example in the issue. Add the requested Automatic-Module-Name entry through the jar manifest configuration, then verify that the built manifest contains org.apache.datasketches.

Written by the indexing model from the issue text.

Description

Hello,

Any plan to add proper jpms/JDK9 module configuration into the library?

Current manifest looks like :

Manifest-Version: 1.0
Build-Jdk-Spec: 25
Build-OS: Mac OS X aarch64 26.1
Build-Tool-Jdk-Spec: 25
GroupId-ArtifactId: org.apache.datasketches:datasketches-java
Implementation-Vendor: The Apache Software Foundation
git-branch: 9.0.X
git-commit-id: f3b334b380feee9f928500de9adb6bbf763fc104
git-commit-tag: 9.0.0-RC1
git-commit-time: 
git-commit-user-email: xxx@yyy.com

An easy way forward would be through an additional Automatic-Module-Name entry, like:

Automatic-Module-Name: org.apache.datasketches

it can be done with something like:

<plugin>
	<groupId>org.apache.maven.plugins</groupId>
	<artifactId>maven-jar-plugin</artifactId>
	<configuration>
		<archive>
			<manifestEntries>
				<Automatic-Module-Name>org.apache.datasketches</Automatic-Module-Name>
			</manifestEntries>
		</archive>
	</configuration>
</plugin>

edit: I would benefit from this going from datasketches 7.X

Dominant language: Java
Stars: 958
Forks: 226
Avg merge: 3d 40m
Merged PRs (30d): 13

Contributor guide

No contributing guide indexed for this repository

First steps

Read the whole issue, then the project's contributing guide.
Comment on the issue to say you are picking it up — it saves two people doing the same work.
Fork the repository and make your change on a branch.
Open a pull request that references the issue number.

Similar issues

Document Hot Rod migration version compatibility for Data Grid 8.6 Open

Difficulty 2/5 1-3 hours Newbie friendliness 82/100

infinispan/infinispan#18150 · Opened Sep 21, 2026
[BUG] Route53Resolver: CreateResolverEndpoint requires IpAddressRequests, but the AWS member is IpAddresses, so no SDK client can call it Open

Difficulty 2/5 1-3 hours Newbie friendliness 84/100

floci-io/floci#4108 · Opened Sep 21, 2026
[BUG] RestGetModelHandlerIT.testGetModel_whenModelIDIsInValid_thenFail depends on test order and fails when run alone Open

untriaged

Difficulty 2/5 1-3 hours Newbie friendliness 82/100

opensearch-project/k-NN#3597 · Opened Sep 21, 2026
Concurrent builder skips 'verify' phase when running 'mvn install' Open

bug

Difficulty 2/5 1-3 hours Newbie friendliness 88/100

apache/maven#13230 · 1 comment · Opened Sep 21, 2026
ComponentGeNRTL leaves lnGamma stale after computing gamma Open

bug

Difficulty 2/5 1-3 hours Newbie friendliness 82/100

equinor/neqsim#3899 · 1 comment · Opened Sep 21, 2026

More Java issues