Gradle

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Fix resolving `DirectoryTee` elements of a `FileCollection`.

Merge pull request #10369 from gradle/sg/regressions/deprecated-classloader

Fix regression

Avoid sharing the same id for the deprecated classloader as the real classloader

Merge pull request #10316 from gradle/breskeby/scan-plugin-2-4-1

Update default scan plugin version to 2.4.1

Merge remote-tracking branch 'origin/blindpirate/fix-10347' into release

* origin/blindpirate/fix-10347:

Override getResources in DefaultDeprecatedClassLoader

Merge pull request #10352 from gradle/jjohannes/duplicated-publication-warning

Turn 'multiple publications with same coordinates' error into warning

Recognize contributor

    • -1
    • +2
    /subprojects/docs/src/docs/release/notes.md
enhanced test source folder detection for eclipse task. (#10320)

Fixes eclipse/buildship#909

Signed-off-by: Christian Dietrich <christian.dietrich@itemis.de>

Turn 'multiple publications with same coordinates' error into warning

This reduces the severity of the error detection introduced in #9466.

Although this situation is technically an error that should be avoided

as it causes information loss in the published result, in some testing

scenarios builds may rely on this behavior. So instead of failing,

Gradle now prints a warning message.

Override getResources in DefaultDeprecatedClassLoader

This fixes https://github.com/gradle/gradle/issues/10347

In https://github.com/gradle/gradle/pull/9898 we introduced a DefaultDeprecatedClassLoader,

which overrides getResource() but not getResources(). This causes some issues.

This PR fixes the issue by correctly overriding getResources() method.

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

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

Deduplicate sign task inputs

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

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
Update default scan plugin version to 2.4.1

Polish release notes

    • -22
    • +33
    /subprojects/docs/src/docs/release/notes.md
Sign task ignores missing files

This is a similar lenient behavior as in the publishing plugins.

Signing will now still work if Gradle Module Metadata was disabled

by disabling the corresponding 'generateMetadataFileFor...' task.

Fix santaTrackerAndroid on release

By resetting it to a state where it works with

the baseline.

    • -1
    • +1
    /subprojects/performance/templates.gradle
Remove other removed plugins from link test

Update license file to include references to licenses

unless otherwise listed, any 3rd party dependency is assumed to be

Apache 2.0

Identify license information for all dependencies