integTest

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

  1. … 3 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 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 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.
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. … 37 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.
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.
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.
Catch up with master

  1. … 414 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.
Allow a capability request without version to be published

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

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. … 10 more files in changeset.
Allow a capability request without version to be published

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

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