Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
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
    • +2
    ./MavenPublishGcsIntegrationTest.groovy
  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
    • +2
    ./MavenPublishGcsIntegrationTest.groovy
  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
    • +2
    ./MavenPublishGcsIntegrationTest.groovy
  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
    • +2
    ./MavenPublishGcsIntegrationTest.groovy
  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
    • +2
    ./MavenPublishGcsIntegrationTest.groovy
  1. … 33 more files in changeset.
Improve error message when build fails because of missing metadata

Gradle 6.0 removed the "artifact" metadata source by default.

This means that if a module is published _only_ with an artifact,

previous version of Gradle would find it, but 6.0 would fail with

a module missing exception.

The problem is that it's hard to realize that the issue comes

from the change of this default artifact sources.

This commit tries to improve the situation by recognizing that

a failure is related to not finding metadata, and in this case

would suggest that if the metadata is missing, it is still

possible that the jar is present.

The drawback of this approach is that we're unsure: if, for

some reason, the module is _really_ absent, then we gave a

wrong advice. This means, in particular, in case of wrong

coordinates.

    • -0
    • +1
    ./MavenGcsRepoErrorsIntegrationTest.groovy
  1. … 12 more files in changeset.
Improve error message when build fails because of missing metadata

Gradle 6.0 removed the "artifact" metadata source by default.

This means that if a module is published _only_ with an artifact,

previous version of Gradle would find it, but 6.0 would fail with

a module missing exception.

The problem is that it's hard to realize that the issue comes

from the change of this default artifact sources.

This commit tries to improve the situation by recognizing that

a failure is related to not finding metadata, and in this case

would suggest that if the metadata is missing, it is still

possible that the jar is present.

The drawback of this approach is that we're unsure: if, for

some reason, the module is _really_ absent, then we gave a

wrong advice. This means, in particular, in case of wrong

coordinates.

    • -0
    • +1
    ./MavenGcsRepoErrorsIntegrationTest.groovy
  1. … 12 more files in changeset.
Improve error message when build fails because of missing metadata

Gradle 6.0 removed the "artifact" metadata source by default.

This means that if a module is published _only_ with an artifact,

previous version of Gradle would find it, but 6.0 would fail with

a module missing exception.

The problem is that it's hard to realize that the issue comes

from the change of this default artifact sources.

This commit tries to improve the situation by recognizing that

a failure is related to not finding metadata, and in this case

would suggest that if the metadata is missing, it is still

possible that the jar is present.

The drawback of this approach is that we're unsure: if, for

some reason, the module is _really_ absent, then we gave a

wrong advice. This means, in particular, in case of wrong

coordinates.

    • -0
    • +1
    ./MavenGcsRepoErrorsIntegrationTest.groovy
  1. … 12 more files in changeset.
Merge resources integration tests

    • -127
    • +0
    ./MavenGcsRepoErrorsIntegrationTest.groovy
    • -115
    • +0
    ./MavenGcsRepoResolveIntegrationTest.groovy
    • -176
    • +0
    ./MavenGcsSnapshotRepoIntegrationTest.groovy
    • -86
    • +0
    ./MavenPublishGcsErrorsIntegrationTest.groovy
    • -83
    • +0
    ./MavenPublishGcsIntegrationTest.groovy
  1. … 119 more files in changeset.
Adjust tests and samples to new metadata sources defaults

    • -2
    • +0
    ./MavenGcsRepoErrorsIntegrationTest.groovy
    • -1
    • +7
    ./MavenGcsSnapshotRepoIntegrationTest.groovy
  1. … 94 more files in changeset.
Adjust tests and samples to new publishing default behavior

    • -1
    • +0
    ./MavenPublishGcsErrorsIntegrationTest.groovy
  1. … 43 more files in changeset.
wip - fix more tests

    • -1
    • +7
    ./MavenGcsSnapshotRepoIntegrationTest.groovy
  1. … 46 more files in changeset.
wip - fix more tests

    • -1
    • +7
    ./MavenGcsSnapshotRepoIntegrationTest.groovy
  1. … 45 more files in changeset.
wip - fix more tests

    • -1
    • +7
    ./MavenGcsSnapshotRepoIntegrationTest.groovy
  1. … 46 more files in changeset.
Adjust tests and samples to new metadata sources defaults

    • -2
    • +0
    ./MavenGcsRepoErrorsIntegrationTest.groovy
  1. … 15 more files in changeset.
Adjust tests and samples to new metadata sources defaults

    • -2
    • +0
    ./MavenGcsRepoErrorsIntegrationTest.groovy
  1. … 15 more files in changeset.
Adjust tests and samples to new metadata sources defaults

    • -2
    • +0
    ./MavenGcsRepoErrorsIntegrationTest.groovy
  1. … 15 more files in changeset.
Adjust tests following Gradle Module Metadata feature preview removal

    • -1
    • +0
    ./MavenPublishGcsErrorsIntegrationTest.groovy
  1. … 29 more files in changeset.
Adjust tests following Gradle Module Metadata feature preview removal

    • -1
    • +0
    ./MavenPublishGcsErrorsIntegrationTest.groovy
  1. … 29 more files in changeset.
Adjust tests following Gradle Module Metadata feature preview removal

    • -1
    • +0
    ./MavenPublishGcsErrorsIntegrationTest.groovy
  1. … 29 more files in changeset.
Fix tests

    • -1
    • +0
    ./MavenPublishGcsErrorsIntegrationTest.groovy
  1. … 3 more files in changeset.
Fix tests

    • -1
    • +0
    ./MavenPublishGcsErrorsIntegrationTest.groovy
  1. … 3 more files in changeset.
Do not use Maven libraries for publishing with `maven-publish`

The use of aether and other Maven libraries was problematic:

- Static state forced us to prohibit concurrent publishing tasks

- It was difficult to control/understand the generated `maven-metadata.xml` files

- Multiple layers of indirection Gradle->Maven->Gradle->Maven made the code

difficult to comprehend and modify

Publishing of snapshot modules is not yet working. This will come in a

subsequent commit.

    • -1
    • +0
    ./MavenPublishGcsErrorsIntegrationTest.groovy
  1. … 11 more files in changeset.
Do not use Maven libraries for publishing with `maven-publish`

The use of aether and other Maven libraries was problematic:

- Static state forced us to prohibit concurrent publishing tasks

- It was difficult to control/understand the generated `maven-metadata.xml` files

- Multiple layers of indirection Gradle->Maven->Gradle->Maven made the code

difficult to comprehend and modify

Publishing of snapshot modules is not yet working. This will come in a

subsequent commit.

    • -1
    • +0
    ./MavenPublishGcsErrorsIntegrationTest.groovy
  1. … 11 more files in changeset.
Do not use Maven libraries for publishing with `maven-publish`

The use of aether and other Maven libraries was problematic:

- Static state forced us to prohibit concurrent publishing tasks

- It was difficult to control/understand the generated `maven-metadata.xml` files

- Multiple layers of indirection Gradle->Maven->Gradle->Maven made the code

difficult to comprehend and modify

Publishing of snapshot modules is not yet working. This will come in a

subsequent commit.

    • -1
    • +0
    ./MavenPublishGcsErrorsIntegrationTest.groovy
  1. … 11 more files in changeset.
Do not use Maven libraries for publishing with `maven-publish`

The use of aether and other Maven libraries was problematic:

- Static state forced us to prohibit concurrent publishing tasks

- It was difficult to control/understand the generated `maven-metadata.xml` files

- Multiple layers of indirection Gradle->Maven->Gradle->Maven made the code

difficult to comprehend and modify

Publishing of snapshot modules is not yet working. This will come in a

subsequent commit.

    • -1
    • +0
    ./MavenPublishGcsErrorsIntegrationTest.groovy
  1. … 11 more files in changeset.
Finalize the value of any task `@Input` property whose getter returns a property instance, at the start of execution of the task.

This means that the property value will not change once the task has started execution, so that the same value is always used during fingerprinting, cache key calculation, validation, when queried by a task action, and so on.

This behaviour only applies to `@Input` properties in this commit. This was just a place to start. Other properties will be added in later commits.

Changes to the property are ignored once the value is finalized implicitly in this way and generate a deprecation warning instead of failing, as would happen after `finalizeValue()` is called. This allows a migration path for task types that can add a new property to represent some input and keep their existing lenient (but now deprecated) behaviour for an existing property backed by the new property. It might prove better to flip this around, let's see.

    • -4
    • +9
    ./MavenGcsRepoErrorsIntegrationTest.groovy
  1. … 61 more files in changeset.
Nag users only once about stable_publishing flag

This was an oversight, it should have used the deprecation

logger, not a normal logger to print the warning.

    • -2
    • +3
    ./MavenPublishGcsErrorsIntegrationTest.groovy
  1. … 27 more files in changeset.
Nag users only once about stable_publishing flag

This was an oversight, it should have used the deprecation

logger, not a normal logger to print the warning.

    • -2
    • +3
    ./MavenPublishGcsErrorsIntegrationTest.groovy
  1. … 28 more files in changeset.
Improve error reporting in case no matching dynamic version is found

This commit improves rendering of errors in case resolution fails because

all versions in a dynamic range are evicted, and that at least one of the

evicted versions was evicted because of attribute matching. The error will

now report the attributes on each tested version, as well as the requested

attributes.

For this, the module not found exception has been updated to carry more

context, and now makes use of the tree formatter for consistency with other

exceptions in the codebase.

    • -2
    • +2
    ./MavenGcsRepoErrorsIntegrationTest.groovy
  1. … 37 more files in changeset.