Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
make inner classes static where possible

Signed-off-by: Steven Crockett <crockett.j.steven@gmail.com>

  1. … 42 more files in changeset.
Annotated new test since merging master to be fixed for instant execution

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

Rename @FailsWithInstantExecution to @ToBeFixedForInstantExecution

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

  1. … 858 more files in changeset.
Merge branch 'master' into eskatos/ie/instantIntegTest-enable

  1. … 5 more files in changeset.
Add test for no version during publishing check

  1. … 1 more file in changeset.
Gradle module metadata: forbid no version at all

With this change, it becomes illegal to create a Gradle Module Metadata

file that has depedencies or constraints declared without any version at

all across all variants.

  1. … 3 more files in changeset.
Gradle module metadata: forbid no version at all

With this change, it becomes illegal to create a Gradle Module Metadata

file that has depedencies or constraints declared without any version at

all across all variants.

  1. … 3 more files in changeset.
Gradle module metadata: forbid no version at all

With this change, it becomes illegal to create a Gradle Module Metadata

file that has depedencies or constraints declared without any version at

all across all variants.

  1. … 1 more file in changeset.
Gradle module metadata: forbid no version at all

With this change, it becomes illegal to create a Gradle Module Metadata

file that has depedencies or constraints declared without any version at

all across all variants.

  1. … 1 more file in changeset.
Merge branch 'master' into eskatos/ie/instantIntegTest-enable

  1. … 8 more files in changeset.
Annotate integ tests failing with instant execution in various projects

removing most of @IgnoreWithInstantExecution annotations

after fixing the @FailsWithInstantExecution rule

and more ci feedback

also make @IgnoreWithInstantExecution require a reason from a fixed set

and add it to the remaining ignores

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

  1. … 122 more files in changeset.
Add interface ProjectDependencyConstraint

Signed-off-by: Vladimir Sitnikov <sitnikov.vladimir@gmail.com>

  1. … 2 more files in changeset.
Add a system property to disable publishing of SHA-256

This commit adds an internal system property which can be used as

a workaround whenever the remote repository doesn't accept SHA-256

and SHA-512 checksums. Gradle is fail-safe when it cannot upload

those files, however, in some situations, the remote repository may

not allow promoting the release if it finds such files. This is the

case in older repositories, or currently with Maven Central.

To disable publication of both SHA-256 and SHA-512 checksums, either:

- add `-Dorg.gradle.internal.publish.checksums.insecure` to the CLI or

- add `org.gradle.internal.publish.checksums.insecure=true` to your

`gradle.properties` file

Fixes #11308

  1. … 6 more files in changeset.
Add a system property to disable publishing of SHA-256

This commit adds an internal system property which can be used as

a workaround whenever the remote repository doesn't accept SHA-256

and SHA-512 checksums. Gradle is fail-safe when it cannot upload

those files, however, in some situations, the remote repository may

not allow promoting the release if it finds such files. This is the

case in older repositories, or currently with Maven Central.

To disable publication of both SHA-256 and SHA-512 checksums, either:

- add `-Dorg.gradle.internal.publish.checksums.insecure` to the CLI or

- add `org.gradle.internal.publish.checksums.insecure=true` to your

`gradle.properties` file

Fixes #11308

  1. … 5 more files in changeset.
Add a system property to disable publishing of SHA-256

This commit adds an internal system property which can be used as

a workaround whenever the remote repository doesn't accept SHA-256

and SHA-512 checksums. Gradle is fail-safe when it cannot upload

those files, however, in some situations, the remote repository may

not allow promoting the release if it finds such files. This is the

case in older repositories, or currently with Maven Central.

To disable publication of both SHA-256 and SHA-512 checksums, either:

- add `-Dorg.gradle.internal.publish.checksums.insecure` to the CLI or

- add `org.gradle.internal.publish.checksums.insecure=true` to your

`gradle.properties` file

Fixes #11308

  1. … 6 more files in changeset.
Allow publication artifacts to be defined as files through providers

*Updated solution based on feedback to #11329*

This used to work in Gradle 5.5 (see #11054).

The combination of #9467 and #6775 broke this.

A builtBy dependency is added if the artifact is a TaskDependencyContainer,

which all Providers are (#9467). This dependency was silently doing

nothing in case of a plain File/String. This became an error (#6775)

because a File/String is nothing that can be resolved to a task.

We now only add a builtBy dependency, if the provider value or content is

actually produced by a task.

  1. … 2 more files in changeset.
Allow publication artifacts to be defined as files through providers

*Updated solution based on feedback to #11329*

This used to work in Gradle 5.5 (see #11054).

The combination of #9467 and #6775 broke this.

A builtBy dependency is added if the artifact is a TaskDependencyContainer,

which all Providers are (#9467). This dependency was silently doing

nothing in case of a plain File/String. This became an error (#6775)

because a File/String is nothing that can be resolved to a task.

We now only add a builtBy dependency, if the provider value or content is

actually produced by a task.

  1. … 2 more files in changeset.
Revert "Allow publication artifacts to be defined as files through providers (#11329)"

This reverts commit a4b79f33fee015bb5faded27426369ad54bae8dd.

  1. … 2 more files in changeset.
Allow publication artifacts to be defined as files through providers (#11329)

This used to work in Gradle 5.5 (see #11054).

The combination of #9467 and #6775 broke this.

A builtBy dependency is added if the artifact is a TaskDependencyContainer,

which all Providers are (#9467). This dependency was silently doing

nothing in case of a plain File/String. This became an error (#6775)

because a File/String is nothing that can be resolved to a task.

We now only add a builtBy dependency, if the provider value or content is

actually produced by a task.

  1. … 2 more files in changeset.
Allow publication artifacts to be defined as files through providers

This used to work in Gradle 5.5 (see #11054).

The combination of #9467 and #6775 broke this.

A builtBy dependency is added if the artifact is a TaskDependencyContainer,

which all Providers are (#9467). This dependency was silently doing

nothing in case of a plain File/String. This became an error (#6775)

because a File/String is nothing that can be resolved to a task.

We now only add a builtBy dependency, if the provider value or content is

actually produced by a task.

  1. … 2 more files in changeset.
Resolve maven publications for project constraints

fixes https://github.com/gradle/gradle/issues/11299

Signed-off-by: Vladimir Sitnikov <sitnikov.vladimir@gmail.com>

  1. … 2 more files in changeset.
Annotate integ tests failing with instant execution in various projects

after third round of CI feedback

much better, no more OOMEs, no more hung builds, no more console

replacement weirdness

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

  1. … 35 more files in changeset.
Annotate integ tests failing with instant execution in various projects

after third round of CI feedback

much better, no more OOMEs, no more hung builds, no more console

replacement weirdness

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

  1. … 37 more files in changeset.
Annotate integ tests failing with instant execution in various projects

after third round of CI feedback

much better, no more OOMEs, no more hung builds, no more console

replacement weirdness

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

  1. … 36 more files in changeset.
Annotate integ tests failing with instant execution in various projects

after third round of CI feedback

much better, no more OOMEs, no more hung builds, no more console

replacement weirdness

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

  1. … 36 more files in changeset.
Annotate integ tests failing with instant execution in various projects

after third round of CI feedback

much better, no more OOMEs, no more hung builds, no more console

replacement weirdness

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

  1. … 36 more files in changeset.
Annotate integ tests failing with instant execution in various projects

after second round of CI feedback

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

  1. … 31 more files in changeset.
Annotate integ tests failing with instant execution in :maven

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

  1. … 25 more files in changeset.
Annotate integ tests failing with instant execution in :maven

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

  1. … 25 more files in changeset.
Rename methods for javadoc and sources jar creation

The new name reflects better what happens exactly when the option is

activated on the java extension.

The publication part is only applicable when a publishing plugin is also

configured.

Issue #11140

  1. … 24 more files in changeset.