From 91650c7f71483650d36999212dfaa1022c3b90d6 Mon Sep 17 00:00:00 2001
From: "Taro L. Saito" <leo@xerial.org>
Date: Sun, 26 Jan 2014 00:12:16 +0900
Subject: [PATCH] Add a link to sbt-sonatype plugin in Using-Sonatype page

---
 src/sphinx/Community/Using-Sonatype.rst | 5 ++++-
 1 file changed, 4 insertions(+), 1 deletion(-)

diff --git a/src/sphinx/Community/Using-Sonatype.rst b/src/sphinx/Community/Using-Sonatype.rst
index 77560258d..a1f4bff51 100644
--- a/src/sphinx/Community/Using-Sonatype.rst
+++ b/src/sphinx/Community/Using-Sonatype.rst
@@ -1,3 +1,6 @@
+
+
+
 =======================
  Deploying to Sonatype
 =======================
@@ -161,7 +164,7 @@ In sbt, run `publishSigned` and you should see something like the following:
 
 After publishing you have to follow the `Release workflow of
 nexus <https://docs.sonatype.org/display/Repository/Sonatype+OSS+Maven+Repository+Usage+Guide#SonatypeOSSMavenRepositoryUsageGuide-8.ReleaseIt>`_.
-In the future, we hope to provide a Nexus sbt plugin that allows the
+`sbt-sonatype plugin <https://github.com/xerial/sbt-sonatype>`_ allows the
 release workflow procedures to be performed directly from sbt.
 
 *Note: Staged releases allow testing across large projects of