Gradle

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Add diagnostics to dependency resolution.

Work around an issue where a `Property` instance may have multiple threads attempting to finalize its value.

Update to RC4

    • -1
    • +1
    /gradle/wrapper/gradle-wrapper.properties
Use HTTP for Groovy docs temporarily

Copy updated precompiled script plugin samples from master

  1. … 44 more files in changeset.
Remove reference to sample output that does no longer exist

Fix missing quotation marks

Fixes #12916

Fix incorrect cache id comparison

Fix java modules transform sample

Update to 6.2 RC2

    • -1
    • +1
    /gradle/wrapper/gradle-wrapper.properties
Improve 'Java modules with transform' sample

Remove module version convention (#12863)

This was set to the project version by default. This breaks the cache

of a compile task even if the version is not used.

We now never set any version be default, but document how to use the

project version as the version of your Java module.

Fixes: https://github.com/gradle/gradle/issues/12860

Update wrapper

    • -1
    • +1
    /gradle/wrapper/gradle-wrapper.properties
Fix memory leak in component metadata rule executor

The cross-build cache for cached component metadata rules stores

instances of realized Maven/Ivy module metadata in memory. The

problem is that those instances shouldn't have any state from

the project/Gradle build attached to them (they should be good

old POJOs) but for implementation reasons, they are not. In

particular, they keep a reference to the attributes factory,

which in turn keeps a reference to the object factory, which,

itself, will leak classloaders.

As a consequence, as more builds get executed, it was _possible_

that the cache would release some entries, but for the classloaders

to be released, it would require _all_ the entries from the same

build to be released from the cache. It turns out this event is

unlikely and as a consequence, builds end up running out of

memory.

This commit fixes the problem by making sure that at the end of

a build, we clear the in-memory cache of component metadata rules.

Therefore, cross-build, we would still read the result of the

execution of rules from the binary, on disk cache, but we would

not reuse in-memory results from previous builds.

This fix has been tested and validated by a user facing this

issue. Memory usage dropped from 11GB of memory to 1GB.

  1. … 6 more files in changeset.
Revert changes to internal handling of JavaExec.classpath (#12852)

This suffers from: https://github.com/gradle/gradle/issues/8755

The revert fixes: https://github.com/gradle/gradle/issues/12832

Merge pull request #12850 from gradle/vv/document-external-plugins-in-precompiled-plugins

Document how to apply external plugins in precompiled plugins

Document how to apply an external plugin in precompiled script plugin

Fix StackOverflowError when += is used from the Groovy DSL to add elements to a `ConfigurableFileCollection` instance.

Restore the ability to define JavaExec.main via task convention (#12836)

Migrate performance database to AWS MySQL

    • -1
    • +1
    /.teamcity/common/performance-test-extensions.kt
Remove sentence about non-existing property from upgrading guide

Update wrapper to 6.4 RC1

    • -1
    • +1
    /gradle/wrapper/gradle-wrapper.properties
Fix link in release notes

    • -1
    • +1
    /subprojects/docs/src/docs/release/notes.md
Minor edit

    • -1
    • +1
    /subprojects/docs/src/docs/release/notes.md
Improve release notes

    • -32
    • +34
    /subprojects/docs/src/docs/release/notes.md
Merge pull request #12822 from gradle/pioterj-patch-1

Update release-features.txt for 6.4

Update release-features.txt

Add suggestion to release notes

    • -2
    • +1
    /subprojects/docs/src/docs/release/notes.md
Improve single lockfile per project documentation

Issue #12450

Polish from additional review

    • -5
    • +7
    /subprojects/docs/src/docs/release/notes.md