Gradle

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Upgrade wrapper to 6.0 nightly

    • -1
    • +1
    /gradle/wrapper/gradle-wrapper.properties
Merge branch 'release'

Rebase performance tests with 5.7-20190722220035+0000 baseline

#10348 might have an influence on the performance of these scenarios.

  1. … 11 more files in changeset.
Merge pull request #10339 from gradle/eskatos/ie/it-santa-tracker

Integration test Santa Tracker with Instant Execution

Rebaseline to lock performance improvements

Publish 5.6.1-20190822230328+0000

Merge remote-tracking branch 'origin/gh/issues/10323' into release

* origin/gh/issues/10323:

Clean up open file handle in properties test

Fix issue with properties object not being isolatable

Merge remote-tracking branch 'origin/sg/regressions/archive-task-props' into release

* origin/sg/regressions/archive-task-props:

Setters for legacy properties backed by Property clear conventions

Reproduce https://github.com/gradle/gradle/issues/10311

Merge remote-tracking branch 'origin/gh/worker-api/no-isolation-classloader' into release

* origin/gh/worker-api/no-isolation-classloader:

Simplify buildscript classpath in composite test

Rename test project name for clarity

Clean up worker composite test

Ensure that no-isolation workers run with the classloader of the submitting thread

Temporarily use 5.6 as the baseline for Santa Tracker `assembleDebug` case.

This was scenario made faster when transform nodes for external files were accidentally not scheduled, at the cost of making the clean cache case much slower. These nodes are now scheduled again, making this scenario slower. Use 5.6 as the baseline to ensure this doesn't become worse than 5.6.

Simplify buildscript classpath in composite test

Rename test project name for clarity

Clean up open file handle in properties test

Fix issue with properties object not being isolatable

Extract fixtures for android-instant-execution tests

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

Rename cleanTemplates to cleanRemoteProjects for clarity

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

Deduplicate sign task inputs

Multiple inputs can be defined that point at the same file.

Integration test Santa Tracker with Instant Execution

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

Refine InstantExecutionAndroidIntegrationTest

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

Align implementations of artifact identifier display names

DefaultModuleComponentArtifactIdentifier now behaves similar as

ComponentFileArtifactIdentifier (showing the full actual file name).

This means that the artifact name used during reporting now

contains the version at the usual position in the file name.

This way it shows the actual file name for artifacts originating

from pom-only maven repositories (except snapshots, which show the

SNAPSHOT placeholder) and ivy repositories with default pattern.

The motivation for this alignment is to get the same representation for

the same file, independent of whether it was sourced from traditional

or Gradle module metadata.

  1. … 18 more files in changeset.
Do not drop variant attributes in results based on maven artifacts

FixedComponentArtifacts dropped the variant attributes (stored in

ConfigurationMetadata) for no clear reason. Because of this, the

attributes in the resolve result differed depending on whether the

variant was constructed from pom or GMM.

This is only affecting the attributes reported in the result. During

matching, which happens earlier, all attributes were already considered.

  1. … 3 more files in changeset.
Merge pull request #10327 from gradle/eskatos/smoke/android-3.5.0

Smoke test Android Gradle Plugin 3.5.0

Module test fixture: add 'category' attribute to api/runtime variants

This reflects the default variant attributes of a published

java component.

Replace `FileResolver.resolveFilesAsTree()` and `compositeFileTree()` with `FileCollectionFactory`.

  1. … 30 more files in changeset.
Replace usages of `FileResolver.resolveFile()` with `FileCollectionFactory.resolving()` or `FileOperations.immutable()`, so that `FileResolver` can be responsible only for converting scalar values to File-ish values.

  1. … 27 more files in changeset.
Clean up worker composite test

Prepare for 5.6.1

    • -0
    • +2
    /subprojects/docs/src/docs/release/notes.md
Setters for legacy properties backed by Property clear conventions

The version property of a archive task by convention is set to

project.version.

In previous releases, archiveTask.version = null would clear the

value of version and we would strip this from the archive file name.

In Gradle 5.6, setting a Property's value to null reverts back to

the convention's value.

To mimic the old behavior, using the legacy setter now overwrites

both the value and the convention. So when setting the property

explicitly to null, the underlying Property now has a null value.

Ensure that no-isolation workers run with the classloader of the submitting thread

This fixes a problem where, in a composite build, a worker can get a context

classloader set to a classloader from another project, which causes a class

mismatch when we attempt to re-hydrate a legacy runnable class in AdapterWorkAction.

We now ensure that the context classloader for no-isolation workers get set

to the context classloader of the thread that submitted the work.

    • -0
    • +1
    /subprojects/workers/workers.gradle.kts