# 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:

                TestCoverage(11, TestType.allVersionsCrossVersion, Os.WINDOWS, JvmCategory.MIN_VERSION_WINDOWS, ALL_CROSS_VERSION_BUCKETS.size),
                TestCoverage(12, TestType.noDaemon, Os.LINUX, JvmCategory.MIN_VERSION, DEFAULT_LINUX_FUNCTIONAL_TEST_BUCKET_SIZE),
                TestCoverage(13, TestType.noDaemon, Os.WINDOWS, JvmCategory.MAX_LTS_VERSION),

# ADR-0003 - Avoid introducing Groovy types to public API

## Date

2024-01-12

## Context

Gradle's public API requires equal access from all JVM-based languages.
Kotlin, Groovy, Java and other JVM-based languages should be able to use the Gradle API without relying on another language's standard library.

Historically, Gradle has shipped with some Groovy types in very prominent APIs.

				"parallelizationMethod":{
					"name":"TestDistribution"
				},
				"subprojects":[
					"composite-builds",
					"workers",
					"plugins-java"
				]
			}
		],
		"testCoverageUuid":12
	},
	{
		"buckets":[
			{
				"parallelizationMethod":{
					"name":"TeamCityParallelTests",
					"numberOfBatches":9
				},
				"subprojects":[
					"dependency-management"
				]

        findLatest("scalatest", "org.scalatest:scalatest_${versionProperties["scala"]}:(3.0,)", versionProperties)
        findLatest("scalatestplus-junit", "org.scalatestplus:junit-4-12_${versionProperties["scala"]}:(3.1,)", versionProperties)

        val groovyVersion = VersionNumber.parse(versionProperties["groovy"] as String)

    "linux" : 895
  }, {
    "testProject" : "nativeMonolithicOverlapping",
    "linux" : 967
  } ]
}, {
  "scenario" : "org.gradle.performance.regression.nativeplatform.RealWorldNativePluginPerformanceTest.build with 12 parallel workers",
  "durations" : [ {
    "testProject" : "nativeMonolithic",
    "linux" : 551
  }, {
    "testProject" : "nativeMonolithicOverlapping",
    "linux" : 539
  } ]
}, {

    "LC_CTYPE",

    "JDK_10",
    "JDK_10_0",
    "JDK_10_0_x64",
    "JDK_10_x64",
    "JDK_11",
    "JDK_11_0",
    "JDK_11_0_x64",
    "JDK_11_x64",
    "JDK_12",
    "JDK_12_0",
    "JDK_12_0_x64",
    "JDK_12_x64",
    "JDK_13",
    "JDK_13_0",
    "JDK_13_0_x64",
    "JDK_13_x64",
    "JDK_14",
    "JDK_14_0",
    "JDK_14_0_x64",
    "JDK_15",
    "JDK_15_0",
    "JDK_15_0_x64",

# ADR-0003 - Avoid introducing Groovy types to public API

## Date

2024-01-12

## Context

Gradle's public API requires equal access from all JVM-based languages.
Kotlin, Groovy, Java, and other JVM-based languages should be able to use the Gradle API without relying on another language's standard library.

Historically, Gradle has shipped with some Groovy types in very prominent APIs.

# 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.

# ADR-0001 - Use Architectural Decision Records

## Date

2023-12-01

## Context

In a distributed team with many subteams, the best solution to communicate decisions is to use a format accessible by everyone in charge of development.

We use *Specification* and *Discovery* documents stored in Google Drive, but they present some downsides: