Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Integrate with Gradle Enterprise plugin 3.0 (#11041)

    • -0
    • +170
    ./internal/scan/config/fixtures/GradleEnterprisePluginFixture.groovy
  1. … 51 more files in changeset.
Add tests to prove resiliency of SHA signature uploads

  1. … 2 more files in changeset.
Add tests to prove resiliency of SHA signature uploads

  1. … 2 more files in changeset.
Add tests to prove resiliency of SHA signature uploads

  1. … 2 more files in changeset.
Add support for sha256/sha512 to ivy publishing

Publication of SHA256 and SHA512 checksums is now enabled

on both the legacy `ivy` and `ivy-publish` plugins.

    • -1
    • +1
    ./test/fixtures/ivy/IvyFileModule.groovy
  1. … 9 more files in changeset.
Add support for sha256/sha512 to ivy publishing

Publication of SHA256 and SHA512 checksums is now enabled

on both the legacy `ivy` and `ivy-publish` plugins.

    • -1
    • +1
    ./test/fixtures/ivy/IvyFileModule.groovy
  1. … 9 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.

    • -1
    • +17
    ./test/fixtures/AbstractModule.groovy
    • -11
    • +47
    ./test/fixtures/maven/AbstractMavenModule.groovy
    • -0
    • +12
    ./test/fixtures/maven/DelegatingMavenModule.java
    • -0
    • +4
    ./test/fixtures/maven/MavenModule.groovy
    • -1
    • +20
    ./test/fixtures/server/http/HttpArtifact.groovy
    • -0
    • +10
    ./test/fixtures/server/http/IvyHttpModule.groovy
    • -0
    • +10
    ./test/fixtures/server/sftp/SftpArtifact.java
  1. … 22 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.

    • -1
    • +17
    ./test/fixtures/AbstractModule.groovy
    • -11
    • +47
    ./test/fixtures/maven/AbstractMavenModule.groovy
    • -0
    • +12
    ./test/fixtures/maven/DelegatingMavenModule.java
    • -0
    • +4
    ./test/fixtures/maven/MavenModule.groovy
    • -1
    • +20
    ./test/fixtures/server/http/HttpArtifact.groovy
    • -0
    • +10
    ./test/fixtures/server/http/IvyHttpModule.groovy
    • -0
    • +11
    ./test/fixtures/server/sftp/SftpArtifact.java
  1. … 22 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.

    • -1
    • +17
    ./test/fixtures/AbstractModule.groovy
    • -11
    • +47
    ./test/fixtures/maven/AbstractMavenModule.groovy
    • -0
    • +12
    ./test/fixtures/maven/DelegatingMavenModule.java
    • -0
    • +4
    ./test/fixtures/maven/MavenModule.groovy
    • -1
    • +20
    ./test/fixtures/server/http/HttpArtifact.groovy
    • -0
    • +10
    ./test/fixtures/server/http/IvyHttpModule.groovy
    • -0
    • +10
    ./test/fixtures/server/sftp/SftpArtifact.java
  1. … 22 more files in changeset.
Fail better when using --scan and an old incompatible scan plugin

  1. … 3 more files in changeset.
Restore method needed for binary compatibility

  1. … 2 more files in changeset.
Update scan support for Gradle Enterprise plugin 3.0

Gradle 6 is now only compatible with this plugin.

    • -0
    • +155
    ./internal/scan/config/fixtures/GradleEnterprisePluginFixture.groovy
  1. … 34 more files in changeset.
Remove samples from -all distribution

  1. … 10 more files in changeset.
Cleanup changeset

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

  1. … 2 more files in changeset.
Add kotlin-eap repo to samples using a sample modifier

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

  1. … 1 more file in changeset.
Add kotlin-eap repo to samples using a sample modifier

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

  1. … 1 more file in changeset.
Add kotlin-eap repo to samples using a sample modifier

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

  1. … 1 more file in changeset.
No more absolute path in metadata cache

Reference to file are now relative to the root of the module cache

instead of being absolute.

This allows moving the full module cache around to be reused with

a different root path.

The path are also normalized, so that they are portable across systems

where the name separator changes.

Issue #1338

  1. … 9 more files in changeset.
No more absolute path in metadata cache

Reference to file are now relative to the root of the module cache

instead of being absolute.

This allows moving the full module cache around to be reused with

a different root path.

The path are also normalized, so that they are portable across systems

where the name separator changes.

Issue #1338

  1. … 9 more files in changeset.
Backport test fixture improvements from 6.0 branch

    • -0
    • +7
    ./test/fixtures/maven/AbstractMavenModule.groovy
  1. … 1 more file in changeset.
Backport test fixture improvements from 6.0 branch

    • -0
    • +7
    ./test/fixtures/maven/AbstractMavenModule.groovy
  1. … 1 more file in changeset.
Backport test fixture improvements from 6.0 branch

    • -0
    • +7
    ./test/fixtures/maven/AbstractMavenModule.groovy
  1. … 1 more file in changeset.
Revert unneeded changes in tests

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

  1. … 9 more files in changeset.
Make http server fixture's handle() thread safe

As stated in the here implemented 'ServerWithExpectations' fixture:

"handlers, as well as failures, need to be thread-safe"

This concrete case was working most of the time since usually there are

not more than one expectations for the same request. But if the

same request is expected several times, and the requests are received

in parallel (as it is the case for metadata download), the handle()

method behaved flaky - by not doing reading and updating of the 'run'

flag as an atomic operation.

    • -1
    • +7
    ./test/fixtures/server/ExpectOne.groovy
  1. … 2 more files in changeset.
Make http server fixture's handle() thread safe

As stated in the here implemented 'ServerWithExpectations' fixture:

"handlers, as well as failures, need to be thread-safe"

This concrete case was working most of the time since usually there are

not more than one expectations for the same request. But if the

same request is expected several times, and the requests are received

in parallel (as it is the case for metadata download), the handle()

method behaved flaky - by not doing reading and updating of the 'run'

flag as an atomic operation.

    • -1
    • +7
    ./test/fixtures/server/ExpectOne.groovy
  1. … 2 more files in changeset.
Make http server fixture's handle() thread safe

As stated in the here implemented 'ServerWithExpectations' fixture:

"handlers, as well as failures, need to be thread-safe"

This concrete case was working most of the time since usually there are

not more than one expectations for the same request. But if the

same request is expected several times, and the requests are received

in parallel (as it is the case for metadata download), the handle()

method behaved flaky - by not doing reading and updating of the 'run'

flag as an atomic operation.

    • -1
    • +7
    ./test/fixtures/server/ExpectOne.groovy
  1. … 2 more files in changeset.
Make http server fixture's handle() thread safe

As stated in the here implemented 'ServerWithExpectations' fixture:

"handlers, as well as failures, need to be thread-safe"

This concrete case was working most of the time since usually there are

not more than one expectations for the same request. But if the

same request is expected several times, and the requests are received

in parallel (as it is the case for metadata download), the handle()

method behaved flaky - by not doing reading and updating of the 'run'

flag as an atomic operation.

    • -1
    • +7
    ./test/fixtures/server/ExpectOne.groovy
  1. … 2 more files in changeset.
Add more synchronization to http server fixture

As stated in the here implemented 'ServerWithExpectations' fixture:

"handlers, as well as failures, need to be thread-safe"

This concrete case was working most of the time since usually there are

not more than one expectations for the same request. But if the

same request is expected several times, and the requests are received

in parallel (as it is the case for metadata download), the handle

method behaved flaky.

Support artifacts with different names in maven module fixture

Such artifacts can actually be addressed by 'dependency artifacts'

through the 'artifact { }' notation inside a dependency declaration;

or in Gradle Module Metadata.

    • -3
    • +4
    ./test/fixtures/maven/AbstractMavenModule.groovy
Support artifacts with different names in maven module fixture

Such artifacts can actually be addressed by 'dependency artifacts'

through the 'artifact { }' notation inside a dependency declaration;

or in Gradle Module Metadata.

    • -3
    • +4
    ./test/fixtures/maven/AbstractMavenModule.groovy