# Development best practices

This is a collection of best practices for Gradle implementation.
Should and should not do's.

## Error messages and suggestions

Traditionally, if an error occurred, the error message and the possible solution were provided to the console via a single String in the corresponding exception.
That meant possible solutions for Problems could be scattered all over the console output.

					"workers",
					"model-core",
					"language-groovy",
					"build-init",
					"logging",
					"plugins-groovy",
					"kotlin-dsl",
					"plugins-java",
					"samples",
					"plugin-development",
					"enterprise"
				]
			}
		],
		"testCoverageUuid":1
	},
	{
		"buckets":[
			{
				"parallelizationMethod":{
					"name":"TeamCityParallelTests",
					"numberOfBatches":8

stpractices.coreinfrastructure.org/projects/4898)

[Gradle](https://gradle.org/) is a build tool with a focus on build automation and support for multi-language development. If you are building, testing, publishing, and deploying software on any platform, Gradle offers a flexible model that can support the entire development lifecycle from compiling and packaging code to publishing websites. Gradle has been designed to support build automation across multiple languages and platforms, including...

  - documentation:
    name: 'documentation'
    subprojects:
      - 'platforms/documentation/'
  - extensibility:
    name: 'extensibility'
    subprojects:
      - 'subprojects/plugin-development/'
      - 'subprojects/plugin-use/'
      - 'subprojects/test-kit/'
  - gradle_enterprise:
    name: 'gradle_enterprise'
    subprojects:
      - 'platforms/enterprise/'
  - ide:
    name: 'ide'

    "path": "platforms/native/platform-native",
    "unitTests": true,
    "functionalTests": true,
    "crossVersionTests": false
  },
  {
    "name": "plugin-development",
    "path": "platforms/extensibility/plugin-development",
    "unitTests": true,
    "functionalTests": true,
    "crossVersionTests": true
  },
  {
    "name": "plugin-use",
    "path": "platforms/extensibility/plugin-use",

- **Execution**: Runs the work efficiently. This includes scheduling, execution, caching and so on.

#### Software development platform

This is a general purpose platform that builds on the core automation platform to add support for the automation of software development.
This includes work such as compiling, testing and documenting software, plus sharing that software via publishing and dependency management.

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

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

There is a `#contributing` channel on the community Slack which you can use
to ask any questions.

## Setting up your development environment

In order to make changes to Gradle, you'll need:

* A [Java Development Kit](http://jdk.java.net/) (JDK) **version 11**. Fixed version is required to use [remote cache](#remote-build-cache). 

- **Execution**: Runs the work efficiently. This includes scheduling, execution, caching and so on.

#### Software development platform

This is a general purpose platform that builds on the core automation platform to add support for the automation of software development.
This includes work such as compiling, testing and documenting software, plus sharing that software via publishing and dependency management.