Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Use org.gradle.api.credentials.PasswordCredentials internally

org.gradle.api.artifacts.repositories.PasswordCredentials was where PasswordCredentials originated before being moved to org.gradle.api.credentials package together with other Credentials implementations.

After this change org.gradle.api.artifacts.repositories.PasswordCredentials will remain to be used only in the public APIs around repositories.

Once its surface area is reduced, we might be able to deprecate it in favor of org.gradle.api.credentials.PasswordCredentials in a subsequent change.

  1. … 14 more files in changeset.
Ignore deprecation warnings in 'resources-http'

  1. … 1 more file in changeset.
Ignore deprecation warnings in 'resources-http'

  1. … 1 more file in changeset.
Ignore deprecation warnings in 'resources-http'

  1. … 1 more file in changeset.
Activate 'strict-compile' for all subprojects

  1. … 149 more files in changeset.
Revert "Evict expired connections in HTTP client"

This reverts commit 046ba24550eb1aeaadd82fdc1eea3555a7d6ee2f.

Merge branch '6126-evict-expired-connections' of https://github.com/s4nk/gradle

* '6126-evict-expired-connections' of https://github.com/s4nk/gradle:

Evict expired connections in HTTP client

Extract key and trust manager factory initializations into private methods

Extract a method for obtaining truststore algorithm

Use private method for truststore password

Extract a method for obtaining truststore

Extract a method for obtaining truststore file

Extract a method for obtaining truststore password

Extract common part from an if statement

Extract a method for initializing key manager factory

Extract a method for initializing keystore

Extract a method for obtaining keystore instance

Use try-with-resources when reading keystore file

Extract a method for obtaining keystore type

Extract a method for obtaining keystore file

Extract a method for obtaining keystore password

Use try-with-resources where possible

Remove null checks for values that are never null

Merge remote-tracking branch 'upstream/master' into fix/optional-keystore-file

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.

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

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

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

  1. … 103 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.
Merge branch '6126-evict-expired-connections' of https://github.com/s4nk/gradle into sg/merges/pr-6222

* '6126-evict-expired-connections' of https://github.com/s4nk/gradle:

Evict expired connections in HTTP client