Gradle

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Align documentation and tests on feature preview API

    • -3
    • +3
    /subprojects/docs/src/docs/release/notes.md
Rename chapter and smaller touch ups (#4305)

"coordinate" -> "coordinates"

    • -1
    • +1
    /buildSrc/src/main/kotlin/build-extensions.kt
    • -7
    • +7
    /gradle/dependenciesMetadataRules.gradle
    • -1
    • +1
    /subprojects/build-init/build-init.gradle
  1. … 46 more files in changeset.
Fix bugs when integrating with running Vintage engine on Spock @Unroll test

Vintage engine will trigger events with type 'TEST' for both test class

and test method, which might cause test hang unexpectedly. This PR identifies

these different test events and fixes this issue.

Massaging of content in troubleshooting dependency resolution (#4287)

Clean up the content in the dependency management Java tutorial (#4272)

    • -0
    • +109
    /subprojects/docs/src/docs/userguide/dependencyManagementForJavaProjects.adoc
Merge pull request #4328 from gradle/wolfs/build-cache/mention-kotlin-android

Mention build cache support for Android and Kotlin

Mention build cache support for Android and Kotlin

Ignore failing test on `noDaemon`

`VisualStudioFileCustomizationIntegrationTest.can specify location of generated files`

has been failing for the no daemon tests.

Removed `BuildIdentifier.isCurrentBuild()`, as this represents _state_ about a build that depends on where the build is being observed from and which prevents a `BuildIdentifier` instance being used as an _identifier_ for the build.

Resolve local artifacts synchronously.

Fixed check for whether a local artifact can be resolved asynchronously.

Replaced a bunch of uses of `BuildIdentifier.isCurrentBuild()` to instead compare the build identifier against the identifier of the current build.

Moved some logic that decides whether or not to resolve an artifact synchronously or asynchronously into the implementation of the artifact, to move it closer to the code that is in a better position to know this.

Detangled `IncludedBuildInternal` from the public model types, so that an `IncludedBuildInternal` has-a public `ConfigurableIncludedBuild` property.

Minor edits to a couple of test classes.

Ignore nested class in JUnit platform test

Moved `IncludedBuildInternal` to live with `IncludedBuildRegistry` so that the registry can reference the internal type and used this to simplify the registry API.

Use GZip to compress payload

Merge pull request #4323 from gradle/dd/dependency-management/local-repo-cache

Prior to this change, local file repositories used a completely separate caching infrastructure for in-memory caching. This made the code difficult to understand, and led to subtle differences (bugs) between resolution against remote and local repositories.

This changeset consolidates the cache infrastructure, changing local file repositories to use the CachingModuleComponentRepository and removing the separate InMemoryCachedModuleComponentRepository. Requests for local repositories continue to bypass the persistent caches: the CachingModuleComponentRepository is provided with in-memory caches for this purpose.

There was a ~5% negative performance impact of these changes when resolving a large dependency graph against a local file repository. This was offset by an improvement to avoid XML Schema validation when parsing Ivy files.

Count only loaded/deleted files/dirs during load

Fix spelling metaData -> metadata

Fix entry counter

Introduce in-memory versions of dependency caches

Currently, local file repositories use a completely separate caching

infrastructure for in-memory caching. This makes the code difficult

to understand, and can lead to subtle differences (bugs) between

resolution against remote and local repositories.

This commit introduces in-memory versions of the four key resolution

caches, which will be used to consolidate caching infrastructure

between local and remote repositories.

These caches are not yet used.

Avoid XML validation for downloaded Ivy descriptor files

XML validation is expensive, and we were paying this cost on every

resolve for a local file repository. While XML validation does provide

some improved error messages for malformed Ivy files, the benefit does

not seem to be enough to justify the cost.

This change improved performance of local (file) Ivy repository by 23%.

XML validation is still performed when publishing Ivy descriptor files

with the `ivy-publish` plugin.

Use same classloader when filtering @Categories in JUnit

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

Previously we load JUnit Categories with application classloader,

which might mismatch with actually classloader (e.g. Powermock)

and result in invalid categories configuration. This PR uses same

classloader with Runner when loading category classes to avoid

this issue.

Fix distribution jar count

Fix failed tests

    • -2
    • +2
    /subprojects/docs/src/docs/release/notes.md
Improve store and load performance

By not using DataInputStream and DataOutputStream.

Also, we now report cache overhead as Unpack build operations

Disable failing perf tests for Swift