Gradle

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Create plugin for shaded jar creation

Turn `org.gradle.api.artifacts.cache` into an internal package

These interfaces are not accessible from public API. Only through

the internal `ResolutionStrategyInternal.getResolutionRules()`.

Hence we remove them from the public API. This includes moving them

from `core-api` to `dependency-management`.

#4390

  1. … 3 more files in changeset.
Move component metadata rule into DependenciesMetadataRulesPlugin

The rule needs to be applied in all subprojects.

Remove code duplication

Replace client module with component metadata rule

Make JavaVersion support JDK 11 and JEP-223 (#4759)

Add JavaVersion.VERSION_11 and support JEP223

Exclude anonymous class in JUnit Platform (#4774)

This fixes https://github.com/gradle/gradle/issues/4544 https://github.com/gradle/gradle/issues/4618

Previously we send anonymous class to JUnit Platform test worker, which caused some issues.

Now they're excluded by name pattern .*\$\d+

Remove remaining Java serialization from the initial build request message sent from the client to the daemon. There is now no Java serialization used between the client and daemon when running builds from the command-line. There is still some when using the Tooling API.

  1. … 10 more files in changeset.
Use Java serialization for less of the initial build request message that travels from the client to daemon.

Don't use Java serialization for the messages between the client and daemon that happen during a command-line build. Some Java serialization is used in a couple of places for the payload of these messages and for some of the messages that happen during a TAPI operation.

Don't use Java serialization for the initial 'build' command sent from the client to daemon. Some of the pieces of the build command (e.g. the `StartParameter`) are still serialized using Java serialization.

  1. … 4 more files in changeset.
Tasks that print output to the console hold it for as long as possible

Fix for Batch scripts not properly signalling a failure in a pipeline when using 'exit /b 1'. Instead generate a real failure that will cause the pipeline to behave correctly.

Signed-off-by: Jason Archer <jasonmarcher@gmail.com>

Up long running task timeout to 30s

Merge pull request #4778 from gradle/lptr/build-cache/clean-up-task-property-utils

Clean up code around TaskPropertyUtils

Render welcome message + release features upon first invocation (#4766)

    • -0
    • +4
    /subprojects/docs/src/docs/release/release-features.txt
Change console tests to require parallel execution only for specific tests

Fix test after fixture changes

Update user guide to reflect new plain console format

    • -12
    • +13
    /subprojects/docs/src/docs/userguide/console.adoc
Make vesion resolution tests more realistic

The first iteration of these tests provided a set of constraints in

a single project: this made it easy to resolve, as we had _all_ of the

constraints available when resolved any of them to a version.

The test has been updated to also use a chain of project dependencies to

bring in the constraints, forcing them to be resolved sequentially:

this exposes a couple of cases that are not supported by the current

implementation.

Merge pull request #4747 from gradle/oehme/apt/incremental/fast-aggregating

Make aggregating annotation processors faster

Use u-test to determine performance regressions

Instead of an arbitrary threshold we now use the Mann-Whitney U test

to calculate how confident we can be in the results.

For now we'll require a 99% confidence before reporting a regression.

We can tweak that value based on whether we miss too many

regressions or report too many non-regressions.

Ensure console tests run with plain, rich and verbose modes

  1. … 5 more files in changeset.
Merge pull request #4763 from gradle/wolfs/kotlin-dsl/tooling-api

Convert tooling-api to kotlin dsl

Consider all 'reject' constraints in conflict resolution

A component can be selected by multiple dependencies, each of which

may bring version constraints. In conflict resolution, we attempt to

find the component with the highest version that also satisfies all

of the constraints for the module.

Previously, we were only considering one of the depenencies for each

component during conflict resolution, which meant we could incorrectly

choose a component version that should be rejected.

This change fixes #4608 by merging the reject constraints for all

incoming dependencies before using them in conflict resolution.

Bump cache layout format for #4765

The scope of each dependency management entry is cached.

Clean up code around TaskPropertyUtils

- Move single-use method to the only place it is called from

- Add Javadoc to property walking methods

Change module type of dependency-management project to CORE

Convert dependency management related subprojects to kotlin-dsl (#4498)

This PR also fixes the dependency declarations wrt. api/impl separation

for these and related projects.

It fixes two places in production/test code where dependencies

leaked into the classpath and the wrong classes where imported.

    • -0
    • +36
    /subprojects/ivy/ivy.gradle.kts
    • -0
    • +47
    /subprojects/maven/maven.gradle.kts
  1. … 7 more files in changeset.
Ignore scopes in <dependencyManagement> if used as BOM (#4775)

Fixes #4765