Repository navigation
Please add a module name (Automatic-Module-Name) to the jar #741
Description
Hi, and thanks for jvector.
The jvector jar has no Java module name. There is no module-info.java in the repo, and the jar's manifest has no Automatic-Module-Name line. I checked 4.0.0-rc.9, 4.0.1 and main.
Today Java only gives it a name by looking at the file name (jvector-4.0.1.jar becomes jvector). That breaks easily if the jar is renamed or if a build tool doesn't do that. Gradle, for example, will not put such a jar on the module path.
This matters because Eclipse Store's gigamap-jvector module says requires jvector. Anyone who builds a modular app on it has to patch the jvector jar in their own build to add a name.
Simple fix: add one line to the manifest in jvector-multirelease/pom.xml:
<manifestEntries>
<Multi-Release>true</Multi-Release>
<Automatic-Module-Name>jvector</Automatic-Module-Name>
</manifestEntries>The name jvector is the same name Java already picks from the file name, so nothing breaks for current users. A real module-info.java would be nicer later, but this one line solves the problem now.
I can send a pull request for this if you like.
Activity
[-]Add Automatic-Module-Name (or module-info) so the jar has a stable JPMS module name[/-][+]Please add a module name (Automatic-Module-Name) to the jar[/+]hrstoyanov commentedon Oct 3, 2026
A follow-up from the same user: a real
module-info.javawould be even better than the manifest line, if you are open to it.I looked at how the jar is built, and it is not a one-file change, so here is what I found:
jvector-base(Java 11),jvector-twentyandjvector-native. The newer classes go underMETA-INF/versions/20andMETA-INF/versions/22.jdk.incubator.vectordoes not exist in Java 11, so the base descriptor cannot mention it. The newer layers would need their ownMETA-INF/versions/N/module-info.class.io.github.jbellis.jvector) and declare theuses/providesfor the service loading inManagementBackendProviderandVectorizationProvider.Suggested order: first the one-line
Automatic-Module-Name: jvector(it fixes the problem for users right away and keeps the name stable), then a propermodule-info.javaonce you have decided how to handle the Java 20 and 22 layers.I am happy to prototype the descriptor for
jvector-basein a pull request and test it with Eclipse Store'sgigamap-jvectormodule, which doesrequires jvector. Tell me which direction you prefer.