Private Maven repositories

Enable Maven in a Ravenstash repository to publish and resolve private JVM artifacts, metadata, and checksums with Maven-compatible repository conventions.

Choose a workflow

Complete the Maven quickstartEnable Maven, deploy one artifact, and resolve it from the selected repository.

Resolve Maven artifactsUse rvs mvn or configure Maven or Gradle with temporary credentials.

Publish Maven artifactsDeploy project output or a prepared artifact through an authenticated Ravenstash target.

Add a protected Maven mirrorResolve approved Maven Central dependencies through an authenticated Ravenstash source.

Maven in Ravenstash

Ravenstash supports authenticated artifact and metadata publication, Maven metadata XML, artifact and checksum downloads, and release and snapshot-style workflows. Maven and Gradle can use the repository format; rvs mvn provides the shortest workflow with temporary settings and credentials.

Maven coordinates, files, URLs, usage, and mirror settings remain separate from other formats enabled in the same Ravenstash repository.

Upstreams and resolution rules

When the repository connects a Maven Central mirror or another private repository, its own artifacts come first and the first upstream that has a name supplies all of its versions. See How upstream package resolution works.

To keep names you own, such as com.acme:*, away from public registries, or to combine versions from several sources, add package resolution rules on the repository’s Rules tab.