integTest

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Revert "Duplicate project name detection"

This reverts commits 404c6cf303d to ffb51fb92f1 and

commit a0a662cbe49019adb08f996ae3df5a23aa222bbe.

Fixes #12315

  1. … 15 more files in changeset.
Ignore tests for instant execution for now

  1. … 1 more file in changeset.
Fix project publication coordinates being changed without notice

Fixes #12281

  1. … 3 more files in changeset.
Fix Unrolled tests with partial success with instant execution

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

  1. … 7 more files in changeset.
Fix Unrolled tests with partial success with instant execution

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

  1. … 18 more files in changeset.
Revert having unique timestamp inside metadata

The attempt at having the unique timestamp inside the metadata file is

busted as it has too many issues and corner cases.

Instead we leave the -SNAPSHOT in there and let Gradle handle the

finding of the file at resolution time.

Issue #12070

  1. … 2 more files in changeset.
Add opt-out to the duplicate project name detection

This commit reworks the project with duplicate names cycle

detection fix by adding an opt-out: because the new behavior

may force existing users to set both the artifactId and groupId

to publications even if they don't publish all projects, this

could be a potential breaking change.

  1. … 6 more files in changeset.
Rephrase warnings for clarity

  1. … 3 more files in changeset.
Fix circular dependencies when project have the same name

Before this commit, during dependency resolution, a synthetic

module version identifier was generated by project, using the

group and name of the project. However, it's possible for a

project in gradle to have the same name as another in the

same build, leading to duplicates. In this case the projects

were mixed together and lead to a circular dependency.

This commit fixes the problem by making sure we generate

distinct module version identifiers for such projects, by

using the full project path as the name instead of the short

name.

This also makes it possible to publish valid publications

when using the maven or ivy publish plugins. However, we detect

this problem early and warn the user that they should overwrite

the project identity in this case.

  1. … 14 more files in changeset.
Fix Gradle Module Metadata referencing stale files

If a file is not published, then it shouldn't appear in GMM.

  1. … 3 more files in changeset.
Do not publish stale signature files

This commit fixes the publication of stale signature files:

prior to this change it was possible that a signature generated

in a previous build for a different artifact was uploaded even

if no signature was generated during the build, which would

lead to inconsistent publications.

In addition, it makes it an error to publish something which

doesn't have the main artifact created (or, at least up-to-date)

in this build. In other words, if the task which generates the

main artifact is disabled, it's an error to publish.

Other stale artifacts are going to be ignored.

Fixes #5136

  1. … 38 more files in changeset.
Treat single version ranges as "required"

This commit changes the way Gradle handles single version

ranges to treat them like Maven does: they are effectively

"exact" version selectors (not strictly).

Fixes #11185

  1. … 5 more files in changeset.
Revert "Remove sourceJar task in favor of sourcesJar (plural)"

This reverts commit a965be46

  1. … 7 more files in changeset.
Remove sourceJar task in favor of sourcesJar (plural)

  1. … 9 more files in changeset.
Allow a capability request without version to be published (#11691)

If a capability is required by a dependency, the request can be made

without specifying a version. This was not fully supported:

- At publishing time, we published 'version: null' (instead of nothing)

- At consuming time, we failed for a missing version (although this is fine)

Both cases are fixed in this commit and test coverage was added.

The test fixtures are extended to work with dependencies published

with a capability requests.

Fixes #11616

  1. … 11 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.
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.
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 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. … 7 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. … 3 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. … 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.
Resolve maven publications for project constraints

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

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

  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. … 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.