Group: Jenesis

Sort by:Popular▼

✓Popular✓Newest

A plugin exposes them by implementing {@link build.jenesis.repository.observation.ObservabilitySource} through the optional default-method pattern its provider SPI already uses for {@code requiredConfig()}; it is discovered with {@link ...

It carries three types and no marks of its own: {@link build.jenesis.repository.icon.IconContributor} - the interface a family's SPI <em>extends</em> so its implementations may declare a mark, together with the identity the console attributes one ...

<p>It exists so that "where does this go in the store" is answered in one place rather than as a string literal in each module that writes there. It used to answer a harder question - which top-level names are reserved, so that a tenant cannot be ...

Its only dependency beyond java.base is the equally minimal, registry-free {@code build.jenesis.repository.observation} SPI (so a capped store can report its {@code jenreg.quota.*} used-vs-available signals), so a format plugin builds on the store ...

A format (Maven, OCI, npm, PyPI, NuGet) is a separate module that requires only this SPI and the storage SPI and {@code provides RepositoryFormat}; the dispatcher discovers them with {@link java.util.ServiceLoader}, so layouts plug in without the ...

<p>It is its own module, and a tiny one, because the callers that need it sit on both sides of a boundary neither should have to cross. {@code PrivateHosts} lived in the format SPI, so the webhook, forwarding and emulator legs in {@code settings} ...

An {@link build.jenesis.repository.importer.ImportSource} enumerates a foreign repository's assets; an {@link build.jenesis.repository.importer.ImportSourceProvider} builds one for a named incumbent from an {@link ...

Everywhere the whole artifact set must be enumerated - garbage collection, retention eviction, every derived-metadata rebuild - goes through {@code ArtifactWalk}, never a private {@code list()} loop. A walk pass is durable in the walked store itself ...

It is deliberately {@code java.base}-light - its only dependency beyond {@code java.base} is the equally minimal {@code build.jenesis.repository.store} SPI (for {@code Features} and {@code ArtifactStore}, which {@code Authorization} reads its grants ...

It {@code provides} an {@link build.jenesis.repository.store.ArtifactStoreProvider} answering to {@code filesystem}, discovered on the module path with {@code ServiceLoader} - the fallback {@code ArtifactStoreProvider.resolve} selects when no other ...

Headless and stateless over the ArtifactStore SPI: it {@code requires} no backend at all and resolves the one named by {@code JENREG_STORE} through {@code ArtifactStoreProvider.resolve} over {@code ServiceLoader}, exactly as it discovers formats - ...

It also carries the cross-publish bridge ({@link build.jenesis.repository.format.java.bridge}) - the {@code ModuleView} contract by which the Maven layout hands a published modular jar to the Jenesis layout for its module view - exported only to ...

A module implements {@link build.jenesis.repository.posture.SafetyAdvisor} through the same optional-method pattern the observation seam uses, is discovered with {@link java.util.ServiceLoader}, and is handed the effective {@link ...

A format reads the flag for a coordinate/version at serve time and translates it to its own native signal (npm's {@code deprecated} string, Cargo's {@code yanked} boolean, ...), and the operator endpoint writes and clears it through the same ...

<p>Both speak the same S3 API through the same modular AWS SDK client; they differ only in the version token and in how a conditional write is expressed. This module owns what they share so a fix to paging, scanning or reading lands in both at once.

It {@code provides} the {@code ModuleView} the Maven format uses to give a published modular jar its module view - the one-way cross-publish, Maven into the module layout; it does not mirror a module back to Maven. Discovered through {@code ...

When a modular jar is published, it cross-publishes the jar's module view into the Jenesis layout over the bridge the shared module exports to just these two: it {@code uses} the {@code ModuleView} the Jenesis format provides. This is the one ...

It requires the format SPI, the storage SPI and Jackson (to read a manifest's media type and the token-auth response, and to write the tag list), no core - because an OCI blob is addressed by its {@code sha256} digest, exactly the {@code blobs/<hex>} ...

Discovered through {@code provides}.

<p>{@code FormatContract} states each documented clause once - publish serves the exact bytes, a {@code HEAD} is answered from metadata without opening the blob, the shared traversal probe vectors are refused at both the request seam and the ...