Gradle

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Let instant execution support `Serializable` beans with only a `writeObject` method

Remove redundant properties

Polish BrokenValueCodec

Clarify lambdas can be made serializable via generic constraints

No need to use a factory

Use WellKnownFileLocations in DefaultCachedClasspathTransformer

Separate the actual cache from DefaultCachedClasspathTransformer

This is needed so that the cache can be observed among the list of CachedJarFileStore's.

Make instant execution static state workaround more lenient

in order to accommodate for upcoming changes in AGP

Signed-off-by: Paul Merlin <paul@gradle.com>

Fix cycle in 'buildNeeded' and 'buildDependents' tasks (#11485)

With the introduction of capabilities, it is possible that a project

depends on another variant of itself. This is the case, for example,

if you apply the 'java-test-fixtures' plugin.

The issue was that in these cases the 'buildNeeded' / 'buildDependents'

tasks would add a dependency to themselves. This is fixed by checking

that the task about to be added as dependency is not the same task for

which the dependencies are calculated.

Fixes #10410

Merge pull request #11476 from gradle/blindpirate/refine-error-message

Fail fast when MSBuild installation can't be found

Refactor `ModuleSource`

The `ModuleSource` concept was a bit messy. It was designed in order

to be able to store the origin of an artifact. Over time, it evolved

into storing more information, like snapshot timestamps, repositories

or content hash.

The code was convoluted because each part of the code was expecting

some kind of module source, but because of delegation, it wasn't

really possible to add/mix more sources.

This commit refactors this concept into a `ModuleSources` concept

which allows storing more information about a module source, in

a safe and consistent manner. No more wrapping/unwrapping, and each

code requiring a specific type of module source can query for it.

  1. … 50 more files in changeset.
Refactor `ModuleSource`

The `ModuleSource` concept was a bit messy. It was designed in order

to be able to store the origin of an artifact. Over time, it evolved

into storing more information, like snapshot timestamps, repositories

or content hash.

The code was convoluted because each part of the code was expecting

some kind of module source, but because of delegation, it wasn't

really possible to add/mix more sources.

This commit refactors this concept into a `ModuleSources` concept

which allows storing more information about a module source, in

a safe and consistent manner. No more wrapping/unwrapping, and each

code requiring a specific type of module source can query for it.

  1. … 48 more files in changeset.
Refactor `ModuleSource`

The `ModuleSource` concept was a bit messy. It was designed in order

to be able to store the origin of an artifact. Over time, it evolved

into storing more information, like snapshot timestamps, repositories

or content hash.

The code was convoluted because each part of the code was expecting

some kind of module source, but because of delegation, it wasn't

really possible to add/mix more sources.

This commit refactors this concept into a `ModuleSources` concept

which allows storing more information about a module source, in

a safe and consistent manner. No more wrapping/unwrapping, and each

code requiring a specific type of module source can query for it.

  1. … 50 more files in changeset.
Refactor `ModuleSource`

The `ModuleSource` concept was a bit messy. It was designed in order

to be able to store the origin of an artifact. Over time, it evolved

into storing more information, like snapshot timestamps, repositories

or content hash.

The code was convoluted because each part of the code was expecting

some kind of module source, but because of delegation, it wasn't

really possible to add/mix more sources.

This commit refactors this concept into a `ModuleSources` concept

which allows storing more information about a module source, in

a safe and consistent manner. No more wrapping/unwrapping, and each

code requiring a specific type of module source can query for it.

  1. … 50 more files in changeset.
Refactor `ModuleSource`

The `ModuleSource` concept was a bit messy. It was designed in order

to be able to store the origin of an artifact. Over time, it evolved

into storing more information, like snapshot timestamps, repositories

or content hash.

The code was convoluted because each part of the code was expecting

some kind of module source, but because of delegation, it wasn't

really possible to add/mix more sources.

This commit refactors this concept into a `ModuleSources` concept

which allows storing more information about a module source, in

a safe and consistent manner. No more wrapping/unwrapping, and each

code requiring a specific type of module source can query for it.

  1. … 49 more files in changeset.
Bump :kotlinDslPlugins version

Signed-off-by: Paul Merlin <paul@gradle.com>

Migrate `DefaultValueSourceProviderFactory` implementation to model-core

Migrate `DefaultValueSourceProviderFactory` implementation to model-core

Migrate `DefaultValueSourceProviderFactory` implementation to model-core

Migrate `DefaultValueSourceProviderFactory` implementation to model-core

Update native platform to a snapshot

Add comments on what we are watching

Visit the snapshot explciitly instead of casting the node

Serialize `ProviderFactory` service references

Serialize `ProviderFactory` service references

Serialize `ProviderFactory` service references

Serialize `ProviderFactory` service references

Better document why we are waiting for changes to be picked up

Move file watching to separate service

This allows us to plug in different native implemetations later.

Upgrade Kotlin to 1.3.61

Signed-off-by: Paul Merlin <paul@gradle.com>