Switch the gradle plugin to gratatouille (#6524)

* switch the plugin to gratatouille

* remove unused file

Author: martinbonnin

build-logic/build.gradle.kts

@@ -53,7 +53,7 @@ dependencies {
   runtimeOnly(libs.sqldelight.plugin)
   runtimeOnly(libs.gradle.publish.plugin)
   runtimeOnly(libs.benmanes.versions)
-  runtimeOnly(libs.gr8)
+  runtimeOnly(libs.gratatouille)
   runtimeOnly(libs.kotlinx.binarycompatibilityvalidator)
 }
 

build-logic/src/main/kotlin/CompilerOptions.kt

@@ -96,14 +96,6 @@ fun Project.configureJavaAndKotlinCompilers(jvmTarget: Int?, kotlinCompilerOptio
   allWarningsAsErrors(true)
 }
 
-fun setTestToolchain(project: Project, test: Test, javaVersion: Int) {
-  val javaToolchains = project.extensions.getByName("javaToolchains") as JavaToolchainService
-  test.javaLauncher.set(javaToolchains.launcherFor {
-    languageVersion.set(JavaLanguageVersion.of(javaVersion))
-  })
-
-}
-
 fun Project.allWarningsAsErrors(allWarningsAsErrors: Boolean) {
   kotlinExtensionOrNull?.forEachCompilerOptions {
     this.allWarningsAsErrors.set(allWarningsAsErrors)

build-logic/src/main/kotlin/Publishing.kt

@@ -238,12 +238,6 @@ private fun Project.configurePublishingInternal() {
           }
         }
 
-        plugins.hasPlugin("com.gradle.plugin-publish") -> {
-          /**
-           * com.gradle.plugin-publish creates all publications
-           */
-        }
-
         plugins.hasPlugin("java-gradle-plugin") -> {
           /**
            * java-gradle-plugin creates 2 publications (one marker and one regular) but without source/javadoc.

build.gradle.kts

@@ -59,8 +59,7 @@ tasks.register("ciPublishRelease") {
 
 tasks.register("ciTestsGradle") {
   description = "Execute the Gradle tests (slow)"
-  dependsOn(":apollo-gradle-plugin:allTests")
-  dependsOn(":apollo-gradle-plugin-external:validatePlugins")
+  dependsOn(":apollo-gradle-plugin:test")
 }
 
 tasks.register("ciTestsNoGradle") {

docs/source/advanced/persisted-queries.mdx

@@ -57,7 +57,7 @@ apollo {
 
 The operation manifest is generated during code generation. This happens automatically every time you build your project, or you can trigger it manually by executing the `generateApolloSources` Gradle task. 
 
-The operation manifest is generated in `build/generated/manifest/apollo/$serviceName/persistedQueryManifest.json`, where `$serviceName` is `"api"` here. The resulting operation manifest looks something like this:
+The operation manifest is generated in `build/generated/manifest/apollo/$serviceName/persistedQueryManifest.json`, where `$serviceName` is `"api"` here. The resulting operation manifest is similar to the following example:
 
 ```json title="persistedQueryManifest.json"
 {

docs/source/advanced/plugin-configuration.mdx

@@ -22,7 +22,7 @@ apollo {
 
 For more advanced usages, below are all Apollo Gradle Plugin options in a single code block. You can also take a look at the [Gradle Plugin recipes](../advanced/plugin-recipes).
 
-Please refer to the [ApolloExtension](https://www.apollographql.com/docs/kotlin/kdoc/apollo-gradle-plugin-external/com.apollographql.apollo.gradle.api/-apollo-extension/index.html) and [Service](https://www.apollographql.com/docs/kotlin/kdoc/apollo-gradle-plugin-external/com.apollographql.apollo.gradle.api/-service/index.html) API reference for details about a specific API.
+Refer to the [ApolloExtension](https://www.apollographql.com/docs/kotlin/kdoc/apollo-gradle-plugin/com.apollographql.apollo.gradle.api/-apollo-extension/index.html) and [Service](https://www.apollographql.com/docs/kotlin/kdoc/apollo-gradle-plugin/com.apollographql.apollo.gradle.api/-service/index.html) API reference for details about each API.
 
 ```kotlin
 apollo {
@@ -70,10 +70,8 @@ apollo {
     mapScalarToJavaObject("MyObject")
 
 
-    // The format to output for the operation manifest. One of "operationOutput", "persistedQueryManifest"
+    // The format to output for the operation manifest. One of "none" (default) or "persistedQueryManifest"
     operationManifestFormat.set("persistedQueryManifest")
-    // The file where to write the operation manifest
-    operationManifest.set(file("build/generated/persistedQueryManifest.json"))
 
     // Whether to generate Kotlin or Java models
     generateKotlinModels.set(true)
@@ -123,11 +121,7 @@ apollo {
     classesForEnumsMatching.set(listOf(".*"))
     // Whether fields with different shape are disallowed to be merged in disjoint types.
     fieldsOnDisjointTypesMustMerge.set(false)
-
-
-    // The directory where the generated models are written.
-    outputDir.set(file("build/generated/apollo"))
-
+    
     // Whether to generate Apollo metadata. Apollo metadata is used for multi-module support.
     generateApolloMetadata.set(true)
     // list of [Regex] patterns matching for types and fields that should be generated whether they are used by queries/fragments in this module or not.

docs/source/caching/declarative-ids.mdx

@@ -79,7 +79,7 @@ extend interface Node @typePolicy(keyFields: "id")
 
 ## Adding `__typename` to your operations
 
-In addition to the key fields, the declarative cache requires the `__typename` of each object by default. These typenames are not included by default as they make query larger for non-cache users. To avoid cache misses, add `__typename` to every selection using [addTypename](https://www.apollographql.com/docs/kotlin/kdoc/apollo-gradle-plugin-external/com.apollographql.apollo.gradle.api/-service/add-typename.html):
+In addition to the key fields, the declarative cache requires the `__typename` of each object by default. These typenames are not included by default because they make the queries larger for users not using the cache. To avoid cache misses, add `__typename` to every selection using [addTypename](https://www.apollographql.com/docs/kotlin/kdoc/apollo-gradle-plugin/com.apollographql.apollo.gradle.api/-service/add-typename.html):
 
 ```kotlin
 apollo {

docs/source/caching/programmatic-ids.mdx

@@ -55,7 +55,7 @@ You can also use the current object's typename to use _different_ cache ID gener
 
 Note that for cache ID generation to work, your GraphQL operations must return whatever fields your custom code relies on (such as `id` above). If a query does not return a required field, the cache ID will be inconsistent, resulting in data duplication.
 Also, for interfaces and unions, `context.field.type.rawType().name` yields the typename as it is declared in the schema, as opposed to the runtime value of the type received in the response. Instead, querying for the `__typename` is safer.
-To make sure `__typename` is included in all operations set the [addTypename](https://www.apollographql.com/docs/kotlin/kdoc/apollo-gradle-plugin-external/com.apollographql.apollo.gradle.api/-service/add-typename.html) gradle config:
+To make sure `__typename` is included in all operations set the [addTypename](https://www.apollographql.com/docs/kotlin/kdoc/apollo-gradle-plugin/com.apollographql.apollo.gradle.api/-service/add-typename.html) gradle config:
 
 ```
 apollo {

docs/source/essentials/modules.mdx

@@ -48,21 +48,13 @@ See ["Apollo Compiler plugins"](https://www.apollographql.com/docs/kotlin/advanc
 
 `apollo-gradle-plugin` contains the Apollo Gradle plugin.
 
-This module shadows and relocates its runtime dependencies to avoid classpath issues. This can make debugging harder in some cases.
-
-See `apollo-gradle-plugin-external` for a version of `apollo-gradle-plugin` that does not shadow its dependencies.
-
 See ["Gradle Plugin Configuration"](https://www.apollographql.com/docs/kotlin/advanced/plugin-configuration/) for how to use the Gradle plugin.
 
-### apollo-gradle-plugin-external
-
-`apollo-gradle-plugin-external` contains the Apollo Gradle plugin.
+### apollo-gradle-plugin-tasks
 
-This module does not shadow its runtime dependencies, making it more prone to Gradle classpath issues.
+`apollo-gradle-plugin-tasks` contains the task implementations for the Apollo Gradle plugin.
 
-See `apollo-gradle-plugin` for a version of `apollo-gradle-plugin-external` that shadow its dependencies.
-
-See ["Gradle Plugin Configuration"](https://www.apollographql.com/docs/kotlin/advanced/plugin-configuration/) for how to use the Gradle plugin.
+This module is loaded in a separate classloader to allow compiler plugins and avoid polluting the main build script classpath. This module is an implementation detail of `apollo-gradle-plugin` and should not be depended on directly.
 
 ### apollo-http-cache
 

gradle.properties

@@ -30,3 +30,6 @@ org.jetbrains.dokka.experimental.tryK2.nowarn=true
 
 # https://kotlinlang.slack.com/archives/C0B8L3U69/p1740063113894839
 kotlin.js.yarn=false
+
+# https://github.com/gradle/gradle/issues/31278
+kotlin.internal.collectFUSMetrics=false