internal

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Fix for convention mapping replacements.

  1. … 6 more files in changeset.
Enable fine grained invalidation for tasks

Add system includes to immutable file locations

    • -0
    • +17
    ./changedetection/state/DefaultWellKnownFileLocations.java
  1. … 4 more files in changeset.
Add system includes to immutable file locations

    • -0
    • +17
    ./changedetection/state/DefaultWellKnownFileLocations.java
  1. … 4 more files in changeset.
Add system includes to immutable file locations

    • -0
    • +17
    ./changedetection/state/DefaultWellKnownFileLocations.java
  1. … 5 more files in changeset.
Always apply all Category disambiguation rules in Java ecosystem

Before, parts of the platform disambiguation were only done when

using the 'java-platform' plugin. However, consumers using other

Java plugins may also require all rules (see #11091)

    • -0
    • +43
    ./artifacts/JavaEcosystemSupport.java
  1. … 5 more files in changeset.
Add properties on `Report` and subtypes to allow wiring using `Providers`. Specifically, add `Report.activated` to replace `enabled` and `outputLocation` to replace destination.

Change the Java base plugin to use these properties instead of convention mapping to attach conventions for the test report locations.

  1. … 25 more files in changeset.
Add properties on `Report` and subtypes to allow wiring using `Providers`. Specifically, add `Report.activated` to replace `enabled` and `outputLocation` to replace destination.

Change the Java base plugin to use these properties instead of convention mapping to attach conventions for the test report locations.

  1. … 25 more files in changeset.
Remove derived enforced-platform variants

Instead, implement them with strict versions for external modules.

  1. … 19 more files in changeset.
Remove derived enforced-platform variants

Instead, implement them with strict versions for external modules.

  1. … 19 more files in changeset.
Remove derived enforced-platform variants

Instead, implement them with strict versions for external modules.

  1. … 19 more files in changeset.
Remove derived enforced-platform variants

Instead, implement them with strict versions for external modules.

  1. … 13 more files in changeset.
Remove derived enforced-platform variants

Instead, implement them with strict versions for external modules.

  1. … 19 more files in changeset.
Remove derived enforced-platform variants

Instead, implement them with strict versions for external modules.

  1. … 19 more files in changeset.
Add disambiguation rule for platforms

    • -0
    • +51
    ./artifacts/JavaEcosystemSupport.java
  1. … 1 more file in changeset.
Make lib/plugins an input

    • -1
    • +1
    ./classpath/DefaultModuleRegistry.java
  1. … 4 more files in changeset.
Invalidate partially when loading from cache

No user code is executed for loading from cache, so we don't need to

guard against anything.

  1. … 3 more files in changeset.
Invalidate partially when loading from cache

No user code is executed for loading from cache, so we don't need to

guard against anything.

  1. … 3 more files in changeset.
Invalidate partially when loading from cache

No user code is executed for loading from cache, so we don't need to

guard against anything.

  1. … 2 more files in changeset.
Invalidate partially when loading from cache

No user code is executed for loading from cache, so we don't need to

guard against anything.

  1. … 3 more files in changeset.
Make paths/names of included builds immutable (#10998)

Changes the “build path” for included builds to be determined at inclusion time based on the directory name, or a user supplied override. Previously, we tried to use the root project name defined in the included build. This caused a lot of complexity due to it not being known until part way through building the included build.

This change also disallows use of `buildSrc` as a project name, as it collides with the `buildSrc` nested build.

  1. … 70 more files in changeset.
Disallow builds defining a project at :buildSrc

This is already prohibited by the composite build machinery if there is

also a real buildSrc project. This change makes the failure earlier and

more obvious.

  1. … 8 more files in changeset.
Track 'changing' and 'client module' information for override metadata

Although these are edge cases, it leads to more consistency and makes

the behavior less dependent on order which may change unexpectedly

through internal optimisations.

  1. … 7 more files in changeset.
A client module defining dependency declaration is always different

Make paths/names of included builds immutable

  1. … 31 more files in changeset.
Use a linked hash set for dependency artifacts

The order can make a difference in repository selection, when

checking if an artifact-only-component containing the artifacts

exists in a repository. In absence of a metadata file, we initially test

for the existence of one artifact to decide if a repository contains

the corresponding artifact-only-component. This is always the first

artifact in the set (which is internally converted into a list).

This change makes sure that the first artifact is always the same

for a build that does not change.

Use a linked hash set for dependency artifacts

The order can make a difference in repository selection, when

checking if an artifact-only-component containing the artifacts

exists in a repository. In absence of a metadata file, we initially test

for the existence of one artifact to decide if a repository contains

the corresponding artifact-only-component. This is always the first

artifact in the set (which is internally converted into a list).

This change makes sure that the first artifact is always the same

for a build that does not change.

Use a linked hash set for dependency artifacts

The order can make a difference in repository selection, when

checking if an artifact-only-component containing the artifacts

exists in a repository. In absence of a metadata file, we initially test

for the existence of one artifact to decide if a repository contains

the corresponding artifact-only-component. This is always the first

artifact in the set (which is internally converted into a list).

This change makes sure that the first artifact is always the same

for a build that does not change.

Use a linked hash set for dependency artifacts

The order can make a difference in repository selection, when

checking if an artifact-only-component containing the artifacts

exists in a repository. In absence of a metadata file, we initially test

for the existence of one artifact to decide if a repository contains

the corresponding artifact-only-component. This is always the first

artifact in the set (which is internally converted into a list).

This change makes sure that the first artifact is always the same

for a build that does not change.

Use a linked hash set for dependency artifacts

The order can make a difference in repository selection, when

checking if an artifact-only-component containing the artifacts

exists in a repository. In absence of a metadata file, we initially test

for the existence of one artifact to decide if a repository contains

the corresponding artifact-only-component. This is always the first

artifact in the set (which is internally converted into a list).

This change makes sure that the first artifact is always the same

for a build that does not change.