integTest

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
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. … 3 more files in changeset.
Revert "Allow publication artifacts to be defined as files through providers (#11329)"

This reverts commit a4b79f33fee015bb5faded27426369ad54bae8dd.

  1. … 3 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. … 3 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. … 3 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.
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.
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. … 23 more files in changeset.
Remove `platform` dsl from constraint handler

These shortcuts define details of a dependency like attributes,

requested capabilities and 'endorse strict' status. These things

can not be defined on constraints. So these methods only cause

inconsistent behavior.

One can use constraints in combination with platforms like this to

control platform versions:

dependencies {

api platform("org:platform")

constraints {

api "org:platform:1.0"

}

}

  1. … 11 more files in changeset.
Remove `platform` dsl from constraint handler

These shortcuts define details of a dependency like attributes,

requested capabilities and 'endorse strict' status. These things

can not be defined on constraints. So these methods only cause

inconsistent behavior.

One can use constraints in combination with platforms like this to

control platform versions:

dependencies {

api platform("org:platform")

constraints {

api "org:platform:1.0"

}

}

  1. … 9 more files in changeset.
Remove `platform` dsl from constraint handler

These shortcuts define details of a dependency like attributes,

requested capabilities and 'endorse strict' status. These things

can not be defined on constraints. So these methods only cause

inconsistent behavior.

One can use constraints in combination with platforms like this to

control platform versions:

dependencies {

api platform("org:platform")

constraints {

api "org:platform:1.0"

}

}

  1. … 12 more files in changeset.
Remove `platform` dsl from constraint handler

These shortcuts define details of a dependency like attributes,

requested capabilities and 'endorse strict' status. These things

can not be defined on constraints. So these methods only cause

inconsistent behavior.

One can use constraints in combination with platforms like this to

control platform versions:

dependencies {

api platform("org:platform")

constraints {

api "org:platform:1.0"

}

}

  1. … 9 more files in changeset.
Fix NPE and tests

  1. … 6 more files in changeset.
Fix publication warning report

An output is no longer presented if all warnings are silenced by variant

name.

Fixes #11111

  1. … 2 more files in changeset.
Fix publication warning report

An output is no longer presented if all warnings are silenced by variant

name.

Fixes #11111

  1. … 2 more files in changeset.
Do not transform UrlBackedArtifactMetadata

There is no need to start accounting for Maven specifics since the

Gradle Module Metadata properly references the exact artifact to pick.

  1. … 1 more file in changeset.
Do not transform UrlBackedArtifactMetadata

There is no need to start accounting for Maven specifics since the

Gradle Module Metadata properly references the exact artifact to pick.

  1. … 1 more file in changeset.
Add tests to prove resiliency of SHA signature uploads

  1. … 2 more files in changeset.
Add tests to prove resiliency of SHA signature uploads

  1. … 2 more files in changeset.
Add tests to prove resiliency of SHA signature uploads

  1. … 2 more files in changeset.
Add tests to prove resiliency of SHA signature uploads

  1. … 2 more files in changeset.
Add tests to prove resiliency of SHA signature uploads

  1. … 2 more files in changeset.
Add sha-256 and sha-512 checksums to `maven-publish`

This commit adds the SHA-256 and SHA-512 checksums in:

- Gradle Module Metadata

- uploads to Maven repositories using the `maven-publish` plugin

The upload of those additional files is failsafe, just in case some

repositories don't support those checksum files.

  1. … 24 more files in changeset.