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 ...

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 jenesis.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 ...

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 ...

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 (filesystem by default; a cloud backend is selected through ArtifactStoreProvider.resolve via {@code JENESIS_STORE}). It runs on a Spring Boot virtual-thread stack ({@code RepositoryApplication}, the ...

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 ...

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 {@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}.

No blob is deleted by a deployment that did not opt into a collector. A {@code GarbageCollector} matches the retention sweeper's shape - {@code plan} is the dry run a maintenance console previews, {@code collect} computes and applies - and is handed ...

Depends on the import SPI, the format SPI (for the shared fetcher) and Jackson; the server discovers it with {@code ServiceLoader}, so Artifactory support is present exactly when this module is on the path.

The requested ecosystem format is named up front; the provider resolves it among the installed {@link build.jenesis.repository.format.RepositoryFormat}s and streams each enumerated coordinate lazily to the orchestrator, which routes it to that ...

It is the read half of the exit story - the outbound mirror of the export endpoint the free server now serves - so a jenesis repository migrates into another jenesis (or is drained by a forwarder) symmetrically with the Nexus and Artifactory ...

Three enumeration strategies stack by availability: a recursive directory-listing walk where the server exposes an autoindex, falling back to the published Nexus repository index ({@code .index/nexus-maven-repository-index.gz}, read with a pure-JDK ...

Depends on the import SPI, the format SPI (for the shared fetcher) and Jackson; the server discovers it with {@code ServiceLoader}, so Nexus support is present exactly when this module is on the path.

The exchange endpoint discovers it with {@code ServiceLoader}; a deployment without this module answers 501 there - and carries none of the OAuth2/JOSE dependency stack, which lives here rather than in the server.

The dispatcher discovers it with {@code ServiceLoader} and names no transport; a deployment without this module serves local content only (a proxy upstream is never consulted, an import is refused). The composed caches are their own {@code ...