Gradle

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Push common `sq` methods up to trait

Let production build environment assertion allow using Java 8 to run the build (#3746)

* Production build environment is Java 8 to run the build

and Java 7 for compilation

and Java 8 for running tests

Signed-off-by: Paul Merlin <paul@gradle.com>

* Account for sys prop name change java7.home -> java7Home

Signed-off-by: Paul Merlin <paul@gradle.com>

Let production build environment assertion allow using Java 8 to run the build (#3746)

and Java 7 for compilation

and Java 8 for running tests

Account for sys prop name change java7.home -> java7Home

Signed-off-by: Paul Merlin <paul@gradle.com>

Remove CompileAllJava7 ci job (#3750)

* Remove CompilleAllJava7

Signed-off-by: Paul Merlin <paul@gradle.com>

* Remove spurious test

Signed-off-by: Paul Merlin <paul@gradle.com>

    • -8
    • +0
    /.teamcity/Gradle_Check/model/CIBuildModel.kt
Enfore looking only for `ivy` or `gradle` metadata when doing resolution

This commit uses the `metadataSources` to make sure that when we re-resolve, we only use the expected metadata source.

This prevents some tests from accidentally passing because we resolve to Ivy after failing with Gradle.

Explicitly use Java 8 to run the distribution builds (#3749)

Signed-off-by: Paul Merlin <paul@gradle.com>

Allow parallel service registry access

Instead of locking around every service access,

allow multiple threads to look up services at

the same time. This requires almost no coordination,,

as most of the state inside a registry is completely

independent of the rest. Every provider can protected its

own state without locking all the others. The only

coordination needed is when stopping, because we need

to ensure that all pending requests are served first.

This is achieved using a request counter.

Resolve published Ivy files twice, with and without Gradle metadata

This commit changes the Ivy publication tests so that we resolve the published files twice:

- once with Gradle metadata

- once without Gradle metadata

Expectations are set on both, using a single entry point (`resolveArtifacts`). This removes the

explosion of `resolveArtifact` methods.

Merge pull request #3700 from gradle/oehme/performance/canonical-snapshotting

Remove tree root canonicalization

Tweak ComponentSelectionReason interface

- rename isCompositeBuild -> isCompositeParticipant;

- tweak javadoc

Signed-off-by: Rene Groeschke <rene@gradle.com>

Remove obsolete LookupContext concept

This is no longer needed since we don't keep

any state during lookups anymore. This removes

some more garbage and makes the code simpler.

Provide both java7.home & java7Home system properties (#3747)

* Provide both java7.home & java7Home system property

Signed-off-by: Paul Merlin <paul@gradle.com>

* Provide both java7.home & java7Home system property

Signed-off-by: Paul Merlin <paul@gradle.com>

Make NormalizedFileSnapshot equals/hashCode faster

Instead of creating a wrapping object and comparing that,

overwrite specialized methods that return primitives which

can be computed in-place.

Make transformed artifact identifiers cheaper

We used to split the transformed file name into an

IvyArtifactName, just to immediately convert it back

to a String that was almost never needed. We now keep

the IvyArtifactName instead.

Sample projects should provide root project name as best practice (#3730)

  1. … 226 more files in changeset.
Merge pull request #3660 from gradle/lacasseio/native/improve-xcode-ide

Polish Xcode support for source dependencies

Use list instead of table for better readability on mobile devices (#3738)

Reworked C/C++ include file analysis to better handle large dependency graphs by generating less garbage and fewer intermediate results.

Usage consistent case for thread display names.

Merge pull request #3670 from gradle/lptr/performance-test-reporting

Report improved performance test results to Slack

Revert unnecessary change

Expose composite build explicitly as ComponentSelectionReason

* to have stronger api to detect composite build as selection reason

just relying on the description method is not strong enough.

* This change adds ComponentSelectionReason#isCompositeBuild() that can

be checked by consumers (e.g. Build Scan plugin) to detect this scenario

Signed-off-by: Rene Groeschke <rene@gradle.com>

Merge pull request #3690 from gradle/eriwen/faster-docs-font-loading

Load docs fonts from Gradle CDN

Merge pull request #3711 from gradle/eriwen/no-docs-autolabel

Remove docs auto labeling

Find service cycles without spending heap memory

Instead of recording the services being requested

in an extra queue, throw an exception on a cycle

instead and enrich it as we go back up the stack.

This completely removes the cost of cycle detection

during normal operation while still giving us proper

error reporting when something goes wrong.

Let the JVM used to run tests in the gradle/gradle build be set by a Gradle/System property (#3735)

Signed-off-by: Paul Merlin <paul@gradle.com>

Let the JVM used to run tests in the gradle/gradle build be set by a Gradle/System property (#3735)

Signed-off-by: Paul Merlin <paul@gradle.com>

Track applied plugins only once

We were tracking plugins both in the plugin

manager as well as in the plugin container.

The container was behaving like any other of

our domain object containers, which is not quite

right, because users cannot add/remove plugins

manually. It now forbids these operations and

uses the store from the plugin manager directly

instead of keeping another copy of it in memory.

Use standard error as the limit to report improvements

Merge pull request #3733 from gradle/lptr/build-cache/clean-up-part-files

Clean up .part files in build cache