Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Fix TAPI tests

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

    • -3
    • +7
    ./fixtures/GradleModuleMetadata.groovy
    • -11
    • +47
    ./fixtures/maven/AbstractMavenModule.groovy
    • -0
    • +12
    ./fixtures/maven/DelegatingMavenModule.java
    • -0
    • +4
    ./fixtures/resource/RemoteArtifact.java
    • -1
    • +20
    ./fixtures/server/http/HttpArtifact.groovy
    • -0
    • +10
    ./fixtures/server/http/IvyHttpModule.groovy
    • -0
    • +10
    ./fixtures/server/http/MavenHttpArtifact.groovy
    • -0
    • +9
    ./fixtures/server/http/MetaDataArtifact.groovy
    • -0
    • +10
    ./fixtures/server/http/PomHttpArtifact.groovy
    • -0
    • +10
    ./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.

    • -3
    • +7
    ./fixtures/GradleModuleMetadata.groovy
    • -11
    • +47
    ./fixtures/maven/AbstractMavenModule.groovy
    • -0
    • +12
    ./fixtures/maven/DelegatingMavenModule.java
    • -0
    • +4
    ./fixtures/resource/RemoteArtifact.java
    • -1
    • +20
    ./fixtures/server/http/HttpArtifact.groovy
    • -0
    • +10
    ./fixtures/server/http/IvyHttpModule.groovy
    • -0
    • +10
    ./fixtures/server/http/MavenHttpArtifact.groovy
    • -0
    • +9
    ./fixtures/server/http/MetaDataArtifact.groovy
    • -0
    • +10
    ./fixtures/server/http/PomHttpArtifact.groovy
    • -0
    • +10
    ./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.

    • -3
    • +7
    ./fixtures/GradleModuleMetadata.groovy
    • -11
    • +47
    ./fixtures/maven/AbstractMavenModule.groovy
    • -0
    • +12
    ./fixtures/maven/DelegatingMavenModule.java
    • -0
    • +4
    ./fixtures/resource/RemoteArtifact.java
    • -1
    • +20
    ./fixtures/server/http/HttpArtifact.groovy
    • -0
    • +10
    ./fixtures/server/http/IvyHttpModule.groovy
    • -0
    • +10
    ./fixtures/server/http/MavenHttpArtifact.groovy
    • -0
    • +9
    ./fixtures/server/http/MetaDataArtifact.groovy
    • -0
    • +10
    ./fixtures/server/http/PomHttpArtifact.groovy
    • -0
    • +11
    ./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.

    • -3
    • +7
    ./fixtures/GradleModuleMetadata.groovy
    • -11
    • +47
    ./fixtures/maven/AbstractMavenModule.groovy
    • -0
    • +12
    ./fixtures/maven/DelegatingMavenModule.java
    • -0
    • +4
    ./fixtures/resource/RemoteArtifact.java
    • -1
    • +20
    ./fixtures/server/http/HttpArtifact.groovy
    • -0
    • +10
    ./fixtures/server/http/IvyHttpModule.groovy
    • -0
    • +10
    ./fixtures/server/http/MavenHttpArtifact.groovy
    • -0
    • +9
    ./fixtures/server/http/MetaDataArtifact.groovy
    • -0
    • +10
    ./fixtures/server/http/PomHttpArtifact.groovy
    • -0
    • +10
    ./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.

    • -3
    • +7
    ./fixtures/GradleModuleMetadata.groovy
    • -11
    • +47
    ./fixtures/maven/AbstractMavenModule.groovy
    • -0
    • +12
    ./fixtures/maven/DelegatingMavenModule.java
    • -0
    • +4
    ./fixtures/resource/RemoteArtifact.java
    • -1
    • +20
    ./fixtures/server/http/HttpArtifact.groovy
    • -0
    • +10
    ./fixtures/server/http/IvyHttpModule.groovy
    • -0
    • +10
    ./fixtures/server/http/MavenHttpArtifact.groovy
    • -0
    • +9
    ./fixtures/server/http/MetaDataArtifact.groovy
    • -0
    • +10
    ./fixtures/server/http/PomHttpArtifact.groovy
    • -0
    • +10
    ./fixtures/server/sftp/SftpArtifact.java
  1. … 22 more files in changeset.
Backport test fixture improvements from 6.0 branch

    • -0
    • +4
    ./fixtures/server/http/MavenHttpModule.groovy
  1. … 1 more file in changeset.
Backport test fixture improvements from 6.0 branch

    • -0
    • +4
    ./fixtures/server/http/MavenHttpModule.groovy
  1. … 1 more file in changeset.
Backport test fixture improvements from 6.0 branch

    • -0
    • +4
    ./fixtures/server/http/MavenHttpModule.groovy
  1. … 1 more file 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.

    • -2
    • +1
    ./fixtures/server/http/HttpServer.groovy
    • -1
    • +1
    ./fixtures/server/sftp/SFTPServer.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.

    • -2
    • +1
    ./fixtures/server/http/HttpServer.groovy
    • -1
    • +1
    ./fixtures/server/sftp/SFTPServer.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.

    • -2
    • +1
    ./fixtures/server/http/HttpServer.groovy
    • -1
    • +1
    ./fixtures/server/sftp/SFTPServer.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.

    • -2
    • +1
    ./fixtures/server/http/HttpServer.groovy
    • -1
    • +1
    ./fixtures/server/sftp/SFTPServer.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.

    • -1
    • +1
    ./fixtures/server/http/HttpServer.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.

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.

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.

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.

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.

Fix snapshot handling with Gradle Module Metadata

This commit fixes a couple of bugs:

1. if Gradle Module Metadata was published and consumed, then

the `changing` flag for the resolved component metadata wouldn't

be set to `true`, which means that snapshot would effectively be

considered as persistent

2. the publish test fixtures were not using the right, timestamped,

version id for the metadata and artifacts in case of unique snapshots,

which caused the resolution to fallback to the POM file

In addition, this fixes the generated module metadata file which

was uploaded _without_ substution the the SNAPSHOT version with

the timestamped version when published on external repositories.

Finally, this highlighted a couple of issues with test fixtures

which were still using Gradle Module Metadata when they shouldn't.

Fixes #10916

    • -2
    • +4
    ./fixtures/gradle/GradleFileModuleAdapter.groovy
  1. … 8 more files in changeset.
Fix snapshot handling with Gradle Module Metadata

This commit fixes a couple of bugs:

1. if Gradle Module Metadata was published and consumed, then

the `changing` flag for the resolved component metadata wouldn't

be set to `true`, which means that snapshot would effectively be

considered as persistent

2. the publish test fixtures were not using the right, timestamped,

version id for the metadata and artifacts in case of unique snapshots,

which caused the resolution to fallback to the POM file

Fixes #10916

    • -2
    • +4
    ./fixtures/gradle/GradleFileModuleAdapter.groovy
  1. … 5 more files in changeset.
Fix snapshot handling with Gradle Module Metadata

This commit fixes a couple of bugs:

1. if Gradle Module Metadata was published and consumed, then

the `changing` flag for the resolved component metadata wouldn't

be set to `true`, which means that snapshot would effectively be

considered as persistent

2. the publish test fixtures were not using the right, timestamped,

version id for the metadata and artifacts in case of unique snapshots,

which caused the resolution to fallback to the POM file

Fixes #10916

    • -2
    • +4
    ./fixtures/gradle/GradleFileModuleAdapter.groovy
  1. … 5 more files in changeset.
Fix snapshot handling with Gradle Module Metadata

This commit fixes a couple of bugs:

1. if Gradle Module Metadata was published and consumed, then

the `changing` flag for the resolved component metadata wouldn't

be set to `true`, which means that snapshot would effectively be

considered as persistent

2. the publish test fixtures were not using the right, timestamped,

version id for the metadata and artifacts in case of unique snapshots,

which caused the resolution to fallback to the POM file

In addition, this fixes the generated module metadata file which

was uploaded _without_ substution the the SNAPSHOT version with

the timestamped version when published on external repositories.

Finally, this highlighted a couple of issues with test fixtures

which were still using Gradle Module Metadata when they shouldn't.

Fixes #10916

    • -2
    • +4
    ./fixtures/gradle/GradleFileModuleAdapter.groovy
  1. … 8 more files in changeset.
Make injected plugins resolvable from included builds and not just buildSrc

    • -18
    • +25
    ./fixtures/plugin/PluginBuilder.groovy
  1. … 4 more files in changeset.
Merge branch 'release' into ldaley/settings-plugins-block

    • -2
    • +2
    ./fixtures/plugin/PluginBuilder.groovy
  1. … 1 more file in changeset.
Improve advice for dealing with insecure HTTP script plugins

    • -0
    • +4
    ./fixtures/server/http/HttpServerFixture.groovy
  1. … 6 more files in changeset.