docs: update docs to account for new gradle-bloop home

Author: ckipp01

docs-gen/src/main/scala/bloop/Docs.scala

@@ -16,7 +16,8 @@ object Docs {
         Map(
           "VERSION" -> Sonatype.releaseBloop.version,
           "LATEST_VERSION" -> bloop.internal.build.BuildInfo.version,
-          "BLOOP_MAVEN_VERSION" -> Sonatype.releaseBloopMaven.version
+          "BLOOP_MAVEN_VERSION" -> Sonatype.releaseBloopMaven.version,
+          "BLOOP_GRADLE_VERSION" -> Sonatype.releaseBloopGradle.version
         )
       )
       .withArgs(args.toList)

docs-gen/src/main/scala/bloop/docs/Sonatype.scala

@@ -24,6 +24,7 @@ object Sonatype {
   lazy val releaseBloop = fetchLatest("bloop-frontend_2.12")
   lazy val releaseBloopMaven = fetchLatest("bloop-maven-plugin")
   lazy val releaseLauncher = fetchLatest("bloop-launcher_2.12")
+  lazy val releaseBloopGradle = fetchLatest("gradle-bloop_2.13")
 
   /** Returns the latest published snapshot release, or the current release if. */
   private def fetchLatest(artifact: String): Release = {

docs/build-tools/gradle.md

@@ -10,6 +10,11 @@ Configuring bloop in your Gradle projects will speed up your Scala
 development significantly. It is highly recommended to use Bloop in Gradle
 because Gradle has a pretty long development cycle and it takes a long time
 to do basic build operations such as compilation or running an application.
+
+The Gradle plugin lives in its own repository at
+[scalacenter/gradle-bloop](https://github.com/scalacenter/gradle-bloop). Please
+do report any issues with the Gradle integration there!
+
 Learn how to get set up by following the instructions below.
 
 <!-- start -->
@@ -29,8 +34,6 @@ Here is a list of the latest Bloop stable and development versions.
 I am going to be replaced by the docs infrastructure.
 ```
 
-
-
 Add bloop to your `build.gradle` with:
 
 ```gradle
@@ -41,12 +44,11 @@ buildscript {
   }
 
   dependencies {
-    classpath 'ch.epfl.scala:gradle-bloop_2.12:@VERSION@'
+    classpath 'ch.epfl.scala:gradle-bloop_2.12:@BLOOP_GRADLE_VERSION@'
   }
 }
 ```
 
-
 Then, enable bloop in all your Gradle projects with:
 
 ```gradle

docs/contributing-guide.md

@@ -28,14 +28,17 @@ If you're looking for the Maven integration, then you'll want to make those
 changes in
 [scalacenter/bloop-maven-plugin](https://github.com/scalacenter/bloop-maven-plugin).
 
+If you're looking to the Gradle integration, then you'll want to make those
+changes in
+[scalacenter/gradle-bloop](https://github.com/scalacenter/gradle-bloop).
+
 ## Project structure
 
 Here's a list of the most important directories in the bloop repositories.
 
 1. `backend` defines low-level compiler APIs wrapping Zinc APIs.
 1. `frontend` defines the core of bloop, the task scheduling, the CLI and all the supported tasks: compilation, testing, running and linking.
-1. `integrations` contains plugins for some of the supported build tools, sbt
-   and Gradle, to extract any build to bloop.
+1. `integrations` contains the sbt plugin to extract any sbt build to bloop.
 
 When contributing to bloop, you will most likely need to modify code in the
 above directories. The next directories define the rest of the project and