Gradle

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Allow distinguishing between errors and warnings emitted in strict mode

Create separate cross build runner class

Fix usage of deprecated configurations in DSL docs

Corrected DLS docs that still referenced a deprecated configuration.

    • -2
    • +2
    /subprojects/docs/src/docs/dsl/org.gradle.plugins.ide.eclipse.model.EclipseWtpComponent.xml
Fix usage of deprecated configurations in DSL docs

Corrected DLS docs that still referenced a deprecated configuration.

    • -2
    • +2
    /subprojects/docs/src/docs/dsl/org.gradle.plugins.ide.eclipse.model.EclipseWtpComponent.xml
Fix usage of deprecated configurations in DSL docs

Corrected DLS docs that still referenced a deprecated configuration.

    • -2
    • +2
    /subprojects/docs/src/docs/dsl/org.gradle.plugins.ide.eclipse.model.EclipseWtpComponent.xml
Fix usage of deprecated configurations in DSL docs

Corrected DLS docs that still referenced a deprecated configuration.

    • -2
    • +2
    /subprojects/docs/src/docs/dsl/org.gradle.plugins.ide.eclipse.model.EclipseWtpComponent.xml
Ensure that errors are actually reported

Fix runtime test case for validates task caching annotations

Migrate "report setters for property of mutable type #type"

Allow types to be reported sometimes for runtime warnings

Rename CrossBuild{ -> GradleInternal}PerformanceTestRunner

Rewrite section on component metadata rules (#10735)

The section was written when the very first version of rules was

introduced and since then only marginally updated.

This is a complete rewrite of the section focusing on explaining

all the metadata modeling features of Gradle Module Metadata

which can be utilized in rules to enrich existing metadata.

The features are described on using real-world use cases.

Related sections are also updated where applicable.

  1. … 45 more files in changeset.
First working versino

Move "task cannot have property with annotation @#annotation.simpleName" back

We cannot even instantiate a task with the problems tested here during runtime.

There are tests for these cases in ArtifactTransformValuesInjectionIntegrationTest.

Remove test output from test events

  1. … 11 more files in changeset.
Remove test output from test events

  1. … 11 more files in changeset.
Remove test output from test events

  1. … 11 more files in changeset.
Remove test output from test events

  1. … 11 more files in changeset.
Add error message in case GMM doesn't declare variants

This commit validates that published Gradle Module Metadata

declares at least one variant when resolved. This is the

counterpart to validation at publication time, but this time

when resolving, in case a user/plugin generates module metadata

in a non-Gradle compatible way.

Add error message in case GMM doesn't declare variants

This commit validates that published Gradle Module Metadata

declares at least one variant when resolved. This is the

counterpart to validation at publication time, but this time

when resolving, in case a user/plugin generates module metadata

in a non-Gradle compatible way.

Update strict version reference

The new semantics were not reflected in the reference documentation for

the `strictly` version qualifier.

Update strict version reference

The new semantics were not reflected in the reference documentation for

the `strictly` version qualifier.

Update strict version reference

The new semantics were not reflected in the reference documentation for

the `strictly` version qualifier.

Update strict version reference

The new semantics were not reflected in the reference documentation for

the `strictly` version qualifier.

Migrate "does not report missing properties for Provider types"

Document Ivy publication differences

There are a couple things that `ivy-publish` does not do compared to the

legacy ivy publication. They are now documented in a migration section

so that users can adapt their build if needed.

Fixes #10427

Document Ivy publication differences

There are a couple things that `ivy-publish` does not do compared to the

legacy ivy publication. They are now documented in a migration section

so that users can adapt their build if needed.

Fixes #10427

Document Ivy publication differences

There are a couple things that `ivy-publish` does not do compared to the

legacy ivy publication. They are now documented in a migration section

so that users can adapt their build if needed.

Fixes #10427

Document Ivy publication differences

There are a couple things that `ivy-publish` does not do compared to the

legacy ivy publication. They are now documented in a migration section

so that users can adapt their build if needed.

Fixes #10427

Ensure that task being validated actually runs during test