Gradle

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
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

Update smoke test plugin version

Update smoke test plugin version

Primitive implementation for TestOutputEvents

  1. … 4 more files in changeset.
Primitive implementation for TestOutputEvents

  1. … 4 more files in changeset.
Primitive implementation for TestOutputEvents

  1. … 4 more files in changeset.
Primitive implementation for TestOutputEvents

  1. … 4 more files in changeset.
Migrate "no problems with Copy task"

Migrate "detects missing annotation on Groovy properties"

Introduce separate properties for Java and Groovy task sources

Migrate "validates task caching annotations"

Migrate "task cannot have property with annotation #annotation.simpleName"

Migrate "task can have property with annotation @#annotation.simpleName"

Warn on publication of non transitive variant

This is effectively not supported in any of the published format.

Warn on publication of non transitive variant

This is effectively not supported in any of the published format.