Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
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.
Remove Maven API usage from javadoc (#11742)

Previously we use -link https://maven.apache.org/ref/3.0.4/maven-model/apidocs/ in javadoc,

which failed the build upon network issues. This commit removes such usages.

  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. … 26 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. … 27 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. … 27 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.
Deprecate types used by the deprecated 'maven' plugin

This is a follow up to #10439

Deprecate types used by the deprecated 'maven' plugin

This is a follow up to #10439

Remove Maven API usage from javadoc

Previously we use -link https://maven.apache.org/ref/3.0.4/maven-model/apidocs/ in javadoc,

which failed the build upon network issues. This commit removes such usages.

  1. … 3 more files in changeset.
Remove Maven API usage from javadoc

Previously we use -link https://maven.apache.org/ref/3.0.4/maven-model/apidocs/ in javadoc,

which failed the build upon network issues. This commit removes such usages.

  1. … 4 more files in changeset.
Catch up with master

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

This reverts commit a965be46

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

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