From df2efe20a6512bab5b767ea0ab8678740edcc330 Mon Sep 17 00:00:00 2001 From: Baruch Sadogursky Date: Thu, 19 Feb 2015 15:37:51 +0200 Subject: [PATCH] Added Artifactory to the list of repository managers --- doc/DEPLOY.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/doc/DEPLOY.md b/doc/DEPLOY.md index 1eda04375..d59ebb477 100644 --- a/doc/DEPLOY.md +++ b/doc/DEPLOY.md @@ -48,10 +48,10 @@ If you don't already have a server running, you can deploy to S3 buckets using the [S3 wagon private](https://github.com/technomancy/s3-wagon-private) plugin. -### Nexus/Archiva +### Artifactory/Nexus/Archiva The most full-featured and complex route is to run a full-fledged -repository manager. Both [Archiva](http://archiva.apache.org/) and +repository manager. Both [Artifactory](http://www.jfrog.com/open-source/#os-arti), [Archiva](http://archiva.apache.org/) and [Nexus](http://nexus.sonatype.org/) provide this. They also proxy to other repositories, so you can set `^:replace` metadata on `:repositories` in project.clj, and dependency downloads will speed up @@ -59,7 +59,7 @@ by quite a bit since Clojars and Maven Central won't need to be checked. The private server will need to be added to the `:repositories` -listing in project.clj. Archiva and Nexus offer separate repositories +listing in project.clj. Artifactory, Archiva and Nexus offer separate repositories for snapshots and releases, so you'll want two entries for them: ```clj