# ADR-0002 - Avoid using Java serialization

## Date

2012-12-01

## Context

In Gradle, we often need to serialize in-memory objects for caching or transmitting them across process barriers, etc.
Java serialization is one way to implement this, however, despite its simplicity of implementation, it has several drawbacks:

src[gradle.soak.integTest]:*..*&&!src:*..*.internal.*&&!src:*..*.internal..*&&(src:org.gradle.||src:org.gradle.api..*||src:org.gradle.authentication..*||src:org.gradle.build..*||src:org.gradle.buildinit..*||src:org.gradle.caching..*||src:org.gradle.concurrent..*||src:org.gradle.deployment..*||src:org.gradle.external.javadoc..*||src:org.gradle.ide..*||src:org.gradle.ivy..*||src:org.gradle.jvm..*||src:org.gradle.language..*||src:org.gradle.maven..*||src:org.gradle.nativepla...

                                "org.gradle.performance.regression.corefeature.FileSystemWatchingPerformanceTest",
                                "assemble for non-abi change with file system watching and configuration caching"
                            ),
                            it
                        )
                    }
                )
            )
        ),
        Stage(

import org.gradle.internal.util.PropertiesUtils
import org.gradle.util.internal.VersionNumber
import org.gradle.work.DisableCachingByDefault
import java.util.Properties


@DisableCachingByDefault(because = "Not worth caching")
abstract class UpdateInitPluginTemplateVersionFile : DefaultTask() {

    private
    val devSuffixes = arrayOf(
        "-SNAP\\d+",
        "-SNAPSHOT",
        "-alpha.*\\d+",
        "-beta.*\\d+",

     * Test if a method is a prime declaration or an overrides that change the signature.
     *
     * There's no way to tell from the byte code that a method overrides the signature
     * of a parent declaration other than crawling up the type hierarchy.
     */
    private
    fun isSignificantDeclaration(methodNode: MethodNode): Boolean {

        if (methodNode.access.isSynthetic) return false

        if (!hasSuperType) return true

    "linux" : 630,
    "windows" : 988,
    "macOs" : 462
  } ]
}, {
  "scenario" : "org.gradle.performance.regression.android.AndroidIncrementalExecutionPerformanceTest.abi change with configuration caching",
  "durations" : [ {
    "testProject" : "nowInAndroidBuild",
    "linux" : 272,
    "windows" : 396,
    "macOs" : 215
  }, {
    "testProject" : "santaTrackerAndroidBuild",
    "linux" : 672,

import org.gradle.work.DisableCachingByDefault
import java.text.SimpleDateFormat
import java.util.Date
import java.util.Properties
import java.util.TimeZone


@DisableCachingByDefault(because = "Not worth caching")
abstract class BuildReceipt : DefaultTask() {
    companion object {
        private
        val timestampFormat = newSimpleDateFormatUTC("yyyyMMddHHmmssZ")

        private

    steps:
    - name: Checkout repository
      uses: actions/checkout@v4
      # Checkout must run before the caching key is computed using the `hashFiles` method

    - name: Cache Gradle Modules
      uses: actions/cache@v4
      with:
        path: |
          ~/.gradle/caches/modules-2/
          ~/.gradle/caches/build-cache-1/

# ADR-0002 - Avoid using Java serialization

## Date

2012-12-01

## Context

In Gradle we often need to serialize in-memory objects for caching, or to transmit them across process barriers, etc.
Java serialization is one way to implement this, however, despite its simplicity of implementation, it has several drawbacks:

- **Performance:**
Java's built-in serialization mechanism is often slower compared to other serialization solutions.

        "per_commit" : [ "linux", "windows", "macOs" ]
      }
    } ]
  }, {
    "testId" : "org.gradle.performance.regression.android.AndroidIncrementalExecutionPerformanceTest.abi change with configuration caching",
    "groups" : [ {
      "testProject" : "nowInAndroidBuild",
      "coverage" : {
        "per_commit" : [ "linux", "windows", "macOs" ]
      }
    }, {
      "testProject" : "santaTrackerAndroidBuild",