Gradle

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Clean release notes and welcome message for 5.3

    • -49
    • +21
    /subprojects/docs/src/docs/release/notes.md
Merge remote-tracking branch 'origin/master-test' into release-test

Change the `ClassLoader` graph that `ValidateTaskProperties` uses to inspect the classes so that property validators can be shared between the runtime and the validation task. They are not actually shared yet.

Change the `ClassLoader` graph that `ValidateTaskProperties` uses to inspect the classes so that the inspector type and Gradle types are reused from the Gradle core `ClassLoader` rather than reloading these types. This will also allow services and state to be reused as well.

Upgrade Kotlin DSL to 1.1.1

Signed-off-by: Rodrigo B. de Oliveira <rodrigo@gradle.com>

Support depending on multiple variants of the same component

This commit changes the resolution engine so that it is possible

to resolve multiple variants of the same component when using

variant-aware dependency management.

Before, in order to have 2 dependencies on the same component

but using different variants, one had to use explicit configuration

dependencies. Now, with this change, it is possible to have

two dependencies on the same component, but with different attributes.

Those components would resolve to different variants.

Special treatment is applied when attributes are declared on constraints:

in this case, we _merge_ the constraint attributes, and make sure that

the edge is computed using the merged attributes. Should they be

incompatible, the build would fail as before.

  1. … 15 more files in changeset.
Support depending on multiple variants of the same component

This commit changes the resolution engine so that it is possible

to resolve multiple variants of the same component when using

variant-aware dependency management.

Before, in order to have 2 dependencies on the same component

but using different variants, one had to use explicit configuration

dependencies. Now, with this change, it is possible to have

two dependencies on the same component, but with different attributes.

Those components would resolve to different variants.

Special treatment is applied when attributes are declared on constraints:

in this case, we _merge_ the constraint attributes, and make sure that

the edge is computed using the merged attributes. Should they be

incompatible, the build would fail as before.

  1. … 15 more files in changeset.
Support depending on multiple variants of the same component

This commit changes the resolution engine so that it is possible

to resolve multiple variants of the same component when using

variant-aware dependency management.

Before, in order to have 2 dependencies on the same component

but using different variants, one had to use explicit configuration

dependencies. Now, with this change, it is possible to have

two dependencies on the same component, but with different attributes.

Those components would resolve to different variants.

Special treatment is applied when attributes are declared on constraints:

in this case, we _merge_ the constraint attributes, and make sure that

the edge is computed using the merged attributes. Should they be

incompatible, the build would fail as before.

  1. … 15 more files in changeset.
Fix link to docs in release notes

    • -1
    • +1
    /subprojects/docs/src/docs/release/notes.md
Split methods required in Worker

  1. … 4 more files in changeset.
Split methods required in Worker

  1. … 4 more files in changeset.
Split methods required in Worker

  1. … 4 more files in changeset.
Move most of org.gradle.internal.reflect to modelCore

The JavaMethod and DirectInstantiator classes are used by the service

and classloading infrastructure in `baseServices`, so I would leave

them there for now.

  1. … 49 more files in changeset.
Move most of org.gradle.internal.reflect to modelCore

The JavaMethod and DirectInstantiator classes are used by the service

and classloading infrastructure in `baseServices`, so I would leave

them there for now.

  1. … 49 more files in changeset.
Move most of org.gradle.internal.reflect to modelCore

The JavaMethod and DirectInstantiator classes are used by the service

and classloading infrastructure in `baseServices`, so I would leave

them there for now.

  1. … 49 more files in changeset.
Move most of org.gradle.internal.reflect to modelCore

The JavaMethod and DirectInstantiator classes are used by the service

and classloading infrastructure in `baseServices`, so I would leave

them there for now.

  1. … 50 more files in changeset.
Invert dependencies of buildCache and coreApi

While it would be great to have a split between domain object, the

tanglement of the current API makes it hard to do so.

For now, let's move the `buildCache` API to `coreApi` and invert the

dependency.

    • -1
    • +0
    /subprojects/core-api/core-api.gradle.kts
  1. … 14 more files in changeset.
Invert dependencies of buildCache and coreApi

While it would be great to have a split between domain object, the

tanglement of the current API makes it hard to do so.

For now, let's move the `buildCache` API to `coreApi` and invert the

dependency.

    • -1
    • +0
    /subprojects/core-api/core-api.gradle.kts
  1. … 10 more files in changeset.
Invert dependencies of buildCache and coreApi

While it would be great to have a split between domain object, the

tanglement of the current API makes it hard to do so.

For now, let's move the `buildCache` API to `coreApi` and invert the

dependency.

    • -1
    • +0
    /subprojects/core-api/core-api.gradle.kts
  1. … 10 more files in changeset.
Don't use propertySpecFactory for input files

  1. … 37 more files in changeset.
Don't use propertySpecFactory for input files

  1. … 36 more files in changeset.
Don't use propertySpecFactory for input files

  1. … 37 more files in changeset.
Fix typo in Kotlin DSL Primer

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

Downgrade javadoc to html4

When we upgraded build JDK to 11, javadoc html was upgrade to html 5 by default.

However, Docbook complaint and some DSL documentations was broken. Now we downgrade

to html 4 by adding -html4 option to javadoc task.

Downgrade javadoc to html4

When we upgraded build JDK to 11, javadoc html was upgrade to html 5 by default.

However, Docbook complaint and some DSL documentations was broken. Now we downgrade

to html 4 by adding -html4 option to javadoc task.

Downgrade javadoc to html4

When we upgraded build JDK to 11, javadoc html was upgrade to html 5 by default.

However, Docbook complaint and some DSL documentations was broken. Now we downgrade

to html 4 by adding -html4 option to javadoc task.

Revert "Fix Javadoc tags with are not supported by HTML5"

This reverts commit 32c8d1337a08c48e7f45b127c4c9416ae195f925.

  1. … 4 more files in changeset.
Revert "Fix Javadoc tags with are not supported by HTML5"

This reverts commit 32c8d1337a08c48e7f45b127c4c9416ae195f925.

  1. … 4 more files in changeset.
Revert "Fix Javadoc tags with are not supported by HTML5"

This reverts commit 32c8d1337a08c48e7f45b127c4c9416ae195f925.

  1. … 4 more files in changeset.
Merge pull request #8169 from gradle/wolfs/property-metadata-fewer-internal

Move back new @Internal annotations