Maven-native publish and install
Use Maven repository URLs in Java, Kotlin, Scala, and JVM builds without moving developers away from Maven.
Ravenstash gives Java, Kotlin, Scala, and broader JVM teams private release and snapshot repositories with Maven-compatible metadata and authenticated artifact delivery.
<repository>
<id>ravenstash</id>
<url>https://maven.pkg.rvsta.sh/x/_wsabc123/_repo1234/</url>
</repository>mvn deploy \
-DaltDeploymentRepository=ravenstash::default::https://maven.push.rvsta.sh/x/_wsabc123/_repo1234/Ravenstash is built to make private package publishing feel familiar for developers and manageable for teams.
Use Maven repository URLs in Java, Kotlin, Scala, and JVM builds without moving developers away from Maven.
Ravenstash provides the repository files Maven builds expect, including metadata, artifacts, and checksums, so dependency resolution stays familiar.
Let Maven builds use approved Maven Central packages through your private repository while Ravenstash caches repeat downloads.
Choose where package files are stored at rest, then serve authenticated downloads through 300+ geographic locations according to real usage.
Connect a public or authenticated Maven package source and use it directly or behind a private repository.
Learn more →Choose a North America or EU at-rest origin, or use storage owned by your organization, without limiting worldwide delivery.
Learn more →Usage-driven caching keeps authenticated downloads close to active developers, CI pipelines, and deployments.
Learn more →Copy the pattern, then replace the sample references with the immutable workspace and repository references shown in Ravenstash.
<repository>
<id>ravenstash</id>
<url>https://maven.pkg.rvsta.sh/x/_wsabc123/_repo1234/</url>
</repository>mvn deploy \
-DaltDeploymentRepository=ravenstash::default::https://maven.push.rvsta.sh/x/_wsabc123/_repo1234/<server>
<id>ravenstash</id>
<username>token</username>
<password>${env.RAVENSTASH_TOKEN}</password>
</server>Yes. Ravenstash supports release and snapshot-style Maven publishing and the repository files Maven builds expect.
No. Ravenstash keeps upstream fallback behind your private repository. It is built for controlled team builds, not an anonymous public mirror.
Yes. Organization admins can create shared repositories and API tokens for CI without tying builds to one developer's account.