Gradle

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Document deprecation of uploadArchives and maven

Document deprecation of uploadArchives and maven

Annotate integ tests failing with instant execution in various projects

after one more round of CI feedback

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

Annotate integ tests failing with instant execution in various projects

after one more round of CI feedback

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

Annotate integ tests failing with instant execution in various projects

after one more round of CI feedback

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

Annotate integ tests failing with instant execution in various projects

after one more round of CI feedback

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

Annotate integ tests failing with instant execution in various projects

after one more round of CI feedback

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

Clarify smoke test about incremental build

Fix for previous commit.

Fix for previous commit.

Fix for previous commit.

Fix for previous commit.

Fix `ClassNotFoundExeception` when loading objects whose class is defined in a build script from the instant execution cache, after recreating the cache from a daemon process that has previously successfully used the cache.

For example, running `gradle taskA`, `gradle taskA`, `gradle taskB`, `gradle taskB` would fail if `taskB` uses types from a build script.

This was happening because the script ClassLoaders are cached and reused, but the association between ClassLoader and scope was lost, and this association is what instant execution uses to know how to load the class.

This change fixes one case of this problem, but the same problem can still happen if the set of build scripts being referenced changes.

  1. … 11 more files in changeset.
Fix `ClassNotFoundExeception` when loading objects whose class is defined in a build script from the instant execution cache, after recreating the cache from a daemon process that has previously successfully used the cache.

For example, running `gradle taskA`, `gradle taskA`, `gradle taskB`, `gradle taskB` would fail if `taskB` uses types from a build script.

This was happening because the script ClassLoaders are cached and reused, but the association between ClassLoader and scope was lost, and this association is what instant execution uses to know how to load the class.

This change fixes one case of this problem, but the same problem can still happen if the set of build scripts being referenced changes.

  1. … 7 more files in changeset.
Fix `ClassNotFoundExeception` when loading objects whose class is defined in a build script from the instant execution cache, after recreating the cache from a daemon process that has previously successfully used the cache.

For example, running `gradle taskA`, `gradle taskA`, `gradle taskB`, `gradle taskB` would fail if `taskB` uses types from a build script.

This was happening because the script ClassLoaders are cached and reused, but the association between ClassLoader and scope was lost, and this association is what instant execution uses to know how to load the class.

This change fixes one case of this problem, but the same problem can still happen if the set of build scripts being referenced changes.

  1. … 11 more files in changeset.
Fix `ClassNotFoundExeception` when loading objects whose class is defined in a build script from the instant execution cache, after recreating the cache from a daemon process that has previously successfully used the cache.

For example, running `gradle taskA`, `gradle taskA`, `gradle taskB`, `gradle taskB` would fail if `taskB` uses types from a build script.

This was happening because the script ClassLoaders are cached and reused, but the association between ClassLoader and scope was lost, and this association is what instant execution uses to know how to load the class.

This change fixes one case of this problem, but the same problem can still happen if the set of build scripts being referenced changes.

  1. … 7 more files in changeset.
Desugar producer attribute if the requesting attribute is desugared (#11372)

This can be the case if an attribute on a dependency is published

and the resolved target of the dependency is a local project.

For example, a published platform dependency to a local java-platform

project.

We support 'Named' and 'Enum' for desugaring as that are the only

non-primitve types we currently allow to be published in Gradle

Module Metadata.

Remove unused class.

Remove unused class.

Remove unused class.

Remove unused class.

Update released version to latest snapshot

Update library versions in build init to latest for 6.2

Clean release notes and welcome message for 6.2

    • -32
    • +11
    /subprojects/docs/src/docs/release/notes.md
Clean accepted API changes

Update version to 6.2

Merge remote-tracking branch 'origin/master-test' into release-test

Publish 6.0.1-20191115004001+0000

Re-enable @IgnoreWithInstantExecution

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

Re-enable @IgnoreWithInstantExecution

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