Jenesis

Introduction

Jenesis Modules is a module-name-addressable mirror of Maven Central. When a module-info.java says requires com.fasterxml.jackson.databind, something has to turn that module name into a downloadable artifact. Jenesis Modules answers that: it records the module name every artifact on Maven Central declares, and serves the mapping over HTTP at repo.jenesis.build - every request is a 302 redirect to the real file on Maven Central, so nothing is re-hosted.

How you use it

The catalogue is an HTTP service, not a file you download. You ask it for a module name and it redirects (HTTP 302) to the jar on Maven Central - so anything that can follow a redirect is a client:

# Resolve a module name to its jar (follow the redirect with -L):
curl -L https://repo.jenesis.build/module/com.fasterxml.jackson.databind

# Pin a version, or ask for a classifier:
curl -L https://repo.jenesis.build/module/com.fasterxml.jackson.databind/2.18.0

There are two main modes: /module/… resolves by the module-info version, while /artifact/… is a transparent Maven proxy keyed by the Maven version - the file extension passes straight through, so /artifact/<name>/<ver>/<name>.pom returns the POM and the route works as a drop-in Maven repository URL. The next chapter covers every mode, POMs and metadata, and classifiers in full.

The Jenesis build tool points at repo.jenesis.build out of the box, so when your module-info.java declares a requires, the build resolves it here automatically - you rarely call the service by hand. The URL shapes are the whole contract, so a mirror that serves the same shapes is a drop-in replacement.

A module can only be resolved if its jar carries a stable name - a real module-info or an Automatic-Module-Name. Artifacts that ship neither cannot be requested by module name; the reports show how much of Maven Central is covered.

What's in this section

  1. Introduction - you are here.
  2. Resolving through repo.jenesis.build - the URL shapes (/module/…, /artifact/…), versions and classifiers, the 302 contract, using it from the build tool and from curl, and pointing at a mirror.
  3. The catalogue & reports - reading the coverage summary, the per-year "top modules" reports, and the drift report to see what is modular and what is not.
  4. How the catalogue is produced - a short, non-code overview: Maven Central is scanned regularly, each artifact's real module name is read, and named vs. automatic modules are distinguished. Background, for trust - not required to use the service.