Gradle

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Let `eval` accept a runtime classpath for the compiled scripts

So the classpath for non-inlined accessors can be injected in the

script ClassLoaders.

Merge pull request #7407 from gradle/lacasseio/lazy/avoid-reaching-for-configurations

Avoid reaching over project boundaries for binary compatibility check

Fix failing tests

Signed-off-by: Felipe Lima <felipe.lima@gmail.com>

Merge pull request #1188 from gradle/eskatos/perf/fix-rmi-leak

Precompute message in order not to leak Project instance

Refine KotlinDslCompilerPlugins

to preallocate two smaller strings ahead and build the whole message

when it's actually needed

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

Accept API change on MavenDeployer

Merge branch 'release'

Merge pull request #7419 from gradle/timyates/scan-plugin-2.0-update

Updated for build scan plugin v2.0

Stop ignoring tests and fix removed deprecated build scan property

Prevent illegal access warnings in IDEA

Loosen test to assert that the incremental mapping is not present in the application descriptor

Loosen test to assert that the incremental mapping is not present in the application descriptor

Code cleanup

Remove WorkIdentifier

Updated for plugin v2.0

Rename WorkResult to ExecutionResult

Convert TimeoutTaskExecuter to TimeoutStep

Fix isolation of processed metadata

Introduce a hash of the component metadata rules, so that we can

cache different processed metadata based on the hash. This is a

performance optimization, which allows setting different processed

metadata on the "cached metadata" instance, based on a rules hash.

The rule hash is more stable when using class-based rules. If not,

then we have instance based rules which are opaque to Gradle, meaning

that we're going to create as many instances of processed metadata

as there are rules instantiated.

  1. … 4 more files in changeset.
Fix isolation of processed metadata

Introduce a hash of the component metadata rules, so that we can

cache different processed metadata based on the hash. This is a

performance optimization, which allows setting different processed

metadata on the "cached metadata" instance, based on a rules hash.

The rule hash is more stable when using class-based rules. If not,

then we have instance based rules which are opaque to Gradle, meaning

that we're going to create as many instances of processed metadata

as there are rules instantiated.

  1. … 4 more files in changeset.
Merge ActionFiringTaskExecuter into ExecutionStep

  1. … 6 more files in changeset.
Precompute message in order not to leak Project instance

The KotlinCompile task logger goes through RMI to the Kotlin Compiler

daemon. Holding a Project instance per task exacerbated a memory leak

in the Kotlin compiler infrastructure.

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

Add more dynamic version examples

I stumbled upon missing a bit more context about the supported version ranges in Gradle. There is also a Issue about that https://github.com/gradle/gradle/issues/5603 though this is not a fully fledged explanation it is a small improvement of the current doc. I would propose to add a additional paragraph e.g. in customizing_dependency_resolution_behavior.adoc

Signed-off-by: Niklas Grebe <niklas.grebe@innogames.com>

Introduce context object for caching of metadata

This will make it easier to add additional data without changing all method signatures.

Introduce context object for caching of metadata

This will make it easier to add additional data without changing all method signatures.

Add 'execution' subproject

    • -0
    • +1
    /.teamcity/Gradle_Check/model/CIBuildModel.kt
Move execute step to new execution model

Revert per-project caches as it has a very large impact on performance

Revert per-project caches as it has a very large impact on performance

Override path sensitivity for `source` in subclasses

We won't change `SourceTask`s default path sensitivity, so let's change

all the subclasses where we know the path sensitivity.

Merge branch 'release'