publish

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.

    • -0
    • +6
    ./internal/GradleModuleMetadataWriter.java
  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.

    • -0
    • +6
    ./internal/GradleModuleMetadataWriter.java
  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

    • -0
    • +22
    ./internal/PublicationArtifactInternal.java
  1. … 36 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

    • -0
    • +22
    ./internal/PublicationArtifactInternal.java
  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

    • -0
    • +22
    ./internal/PublicationArtifactInternal.java
  1. … 37 more files in changeset.
Catch up with master

    • -7
    • +22
    ./internal/GradleModuleMetadataWriter.java
  1. … 415 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
    • +3
    ./internal/GradleModuleMetadataWriter.java
  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
    • +3
    ./internal/GradleModuleMetadataWriter.java
  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
    • +3
    ./internal/GradleModuleMetadataWriter.java
  1. … 11 more files in changeset.
Introduce a checksum file cache service

This service is responsible for caching the checksums computed from

local file system. Because it's also used for dependency verification

writing and checking, this cache uses the existing infrastructure which

makes sure that if a file is updated locally, we expire the entry in

the cache.

This is done because there are lots of places in the code where we

used the legacy `HashUtil` class, which has no caching whatsoever.

It's, however, quite common to have a build which generates sha1

checksums multiple times for the same file. For example, during

publication.

    • -8
    • +14
    ./internal/GradleModuleMetadataWriter.java
  1. … 101 more files in changeset.
Introduce a checksum file cache service

This service is responsible for caching the checksums computed from

local file system. Because it's also used for dependency verification

writing and checking, this cache uses the existing infrastructure which

makes sure that if a file is updated locally, we expire the entry in

the cache.

This is done because there are lots of places in the code where we

used the legacy `HashUtil` class, which has no caching whatsoever.

It's, however, quite common to have a build which generates sha1

checksums multiple times for the same file. For example, during

publication.

    • -8
    • +14
    ./internal/GradleModuleMetadataWriter.java
  1. … 101 more files in changeset.
Introduce a checksum file cache service

This service is responsible for caching the checksums computed from

local file system. Because it's also used for dependency verification

writing and checking, this cache uses the existing infrastructure which

makes sure that if a file is updated locally, we expire the entry in

the cache.

This is done because there are lots of places in the code where we

used the legacy `HashUtil` class, which has no caching whatsoever.

It's, however, quite common to have a build which generates sha1

checksums multiple times for the same file. For example, during

publication.

    • -8
    • +14
    ./internal/GradleModuleMetadataWriter.java
  1. … 101 more files in changeset.
Introduce a checksum file cache service

This service is responsible for caching the checksums computed from

local file system. Because it's also used for dependency verification

writing and checking, this cache uses the existing infrastructure which

makes sure that if a file is updated locally, we expire the entry in

the cache.

This is done because there are lots of places in the code where we

used the legacy `HashUtil` class, which has no caching whatsoever.

It's, however, quite common to have a build which generates sha1

checksums multiple times for the same file. For example, during

publication.

    • -8
    • +14
    ./internal/GradleModuleMetadataWriter.java
  1. … 102 more files in changeset.
Write capabilities in available-at variants

This is required because variant selection will use the local attributes

and capabilities, adding the real module as a dependency in the current

implementation.

    • -2
    • +5
    ./internal/GradleModuleMetadataWriter.java
  1. … 1 more file in changeset.
Write capabilities in available-at variants

This is required because variant selection will use the local attributes

and capabilities, adding the real module as a dependency in the current

implementation.

    • -2
    • +5
    ./internal/GradleModuleMetadataWriter.java
  1. … 1 more file in changeset.
Write capabilities in available-at variants

This is required because variant selection will use the local attributes

and capabilities, adding the real module as a dependency in the current

implementation.

    • -2
    • +5
    ./internal/GradleModuleMetadataWriter.java
  1. … 1 more file in changeset.
Write capabilities in available-at variants

This is required because variant selection will use the local attributes

and capabilities, adding the real module as a dependency in the current

implementation.

    • -2
    • +5
    ./internal/GradleModuleMetadataWriter.java
  1. … 1 more file in changeset.
Write capabilities in available-at variants

This is required because variant selection will use the local attributes

and capabilities, adding the real module as a dependency in the current

implementation.

    • -2
    • +5
    ./internal/GradleModuleMetadataWriter.java
  1. … 1 more file in changeset.
Write capabilities in available-at variants

This is required because variant selection will use the local attributes

and capabilities, adding the real module as a dependency in the current

implementation.

    • -2
    • +5
    ./internal/GradleModuleMetadataWriter.java
  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.

    • -15
    • +41
    ./internal/GradleModuleMetadataWriter.java
  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.

    • -15
    • +41
    ./internal/GradleModuleMetadataWriter.java
  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.

    • -15
    • +41
    ./internal/GradleModuleMetadataWriter.java
  1. … 2 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.

    • -15
    • +41
    ./internal/GradleModuleMetadataWriter.java
  1. … 2 more files in changeset.
Add interface ProjectDependencyConstraint

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

    • -4
    • +2
    ./internal/GradleModuleMetadataWriter.java
  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>

    • -6
    • +21
    ./internal/GradleModuleMetadataWriter.java
  1. … 3 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. … 3 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.

    • -0
    • +4
    ./internal/GradleModuleMetadataWriter.java
  1. … 33 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.

    • -0
    • +4
    ./internal/GradleModuleMetadataWriter.java
  1. … 33 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.

    • -0
    • +4
    ./internal/GradleModuleMetadataWriter.java
  1. … 33 more files in changeset.