Gradle

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Bump the metadata cache layout version

Include worker process in kill pattern on Windows

Fix runner so that features with `@Unroll` are reported with a human readable name

Changed C/C++ dependency analysis to understand preprocessor token concatenation expressions in macro bodies (eg X##Y).

Revert "Temporarily ignore performance test"

This reverts commit d0bcb0ea84418325f230b3bccb248efbcde133ca.

Move `DependencyMetadata.force` to `LocalOriginDependencyMetadata`

We only honour the 'force' attribute for first-level dependencies, so it is

only valid for dependencies described in the build script. (We never

supported the 'force' attribute when defined in Ivy.xml).

Merge pull request #3597 from gradle/lacasseio/ci-health/windows-failure

Improve leaking process kill pattern to match Play app

Merge branch 'dd/dependency-management/dependency-metadata'

Temporarily ignore performance test

This test is failing after the refactorings, and I'd prefer to optimize

after merging.

Merge pull request #3600 from gradle/dd/4.4/shadow-plugin-fix

Fix constructor maintained for backward compatibility with shadow plugin 1.2.4

Merge pull request #3558 from gradle/oehme/performance/fs-mirror

Reuse cached snapshots of unfiltered trees

Fix build

It should run on windows

Add deprecation warning about internal constructor use by shadow plugin

Fix constuctor retained for compatibility with shadow plugin v1.2.x

Transfer test repo to Gradle

Handle broken packaging types gracefully

Some POMs on Maven Central use profiles to determine

important information like their packaging type. The

result are unreplaced variables like ${packaging.type}.

Until now we would send requests with these unresolved

variables to remote repositories, which would in some

cases just slow down resolution and in other cases break

resolution.

Instead we now sanity check substitution variables and don't

even do a remote request if we find something that is definitely

not a valid name/type/extension/version. This makes resolution

fail faster in some cases and gracefully fall back in other cases.

See https://github.com/gradle/gradle/issues/3065 for a case that

now gracefully falls back to downloading the jar, which is what

Maven would also do in this case.

Fix Configuration.withDependencies example in Javadoc

fixes #3598

Merge pull request #3583 from gradle/oehme/performance/attribute-matching

Remove double bookkeeping in attribute matching

Cache `latest.integration` selected version for source dependency

Improve leaking process kill pattern to match Play app

Add Android caching smoke test

Using Santa Tracker

Re-add smoke test for older version of Shadow plugin (1.2.4)

At this time, shadow-1.2.x is one of the most downloaded plugins, so we'd

like to keep it working until the next major release.

This test shows that Gradle 4.4-rc-1 is broken with Shadow-1.2.4.

Add getter for DependencyConstraintHandler

Move build script DSL generation inside BuildScriptBuilder

By providing constructs that abstract build script operations,

centralizing groovy/kotlin snippets into BuildScriptBuilder impl,

removing groovy/kotlin snippets from all over the place.

Implementation is private and limited to the use cases required Today.

This should be enhanced as new requirements are needed.

Migrate `ComponentMetadataRulesIntegrationTest` to cross-repository test fixtures

Add unit test for system header arguments

Merge pull request #3578 from gradle/oehme/performance/dependency-graph

Replace hash sets with linked lists in dependency graph

Ignore test on cygwin

The test fails since system header discovery does not yet work correctly

on cygwin.

See gradle/stable-native#282

Add inherit, project dependency, include tests for dependency constraints

Implement smarter strategy to resolve sources

This commit changes the way we find sources, by only looking into the appropriate repository. If the

version is a released version, then we will only look into the `distributions` repository. If it's

a snapshot, then we will look into the `distributions-snapshot` repository.

However, it's possible that this project depends on a Kotlin DSL custom distribution for which the

sources haven't been published. So to make it possible to resolve, we use a version range, ending

with the current version, and starting with the previous minor.