DefaultMavenArtifactRepositoryTest.groovy

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Move credentials provider factory interface to core-api module

    • -1
    • +1
    ./DefaultMavenArtifactRepositoryTest.groovy
  1. … 17 more files in changeset.
Allow to use repository name as credentials identity

    • -1
    • +3
    ./DefaultMavenArtifactRepositoryTest.groovy
  1. … 13 more files in changeset.
Fix dependency management unit tests - use object factory for artifact repositories

    • -2
    • +1
    ./DefaultMavenArtifactRepositoryTest.groovy
  1. … 5 more files in changeset.
Fix merging conflicts with master

Signed-off-by: Roberto Perez Alcolea <rperezalcolea@netflix.com>

    • -9
    • +9
    ./DefaultMavenArtifactRepositoryTest.groovy
  1. … 3 more files in changeset.
Add documentation links for insecure url deprecations

    • -2
    • +1
    ./DefaultMavenArtifactRepositoryTest.groovy
  1. … 10 more files in changeset.
Initial steps towards a 2-stage dependency cache

This commit introduces the infrastructure required to get a 2-stage

dependency cache, consisting of a read-only, shareable cache and

a read-write local mutable cache.

The read-only cache would typically be mounted on Docker images.

Only infrastructure, no tests yet.

    • -4
    • +4
    ./DefaultMavenArtifactRepositoryTest.groovy
  1. … 82 more files in changeset.
Initial steps towards a 2-stage dependency cache

This commit introduces the infrastructure required to get a 2-stage

dependency cache, consisting of a read-only, shareable cache and

a read-write local mutable cache.

The read-only cache would typically be mounted on Docker images.

Only infrastructure, no tests yet.

    • -4
    • +4
    ./DefaultMavenArtifactRepositoryTest.groovy
  1. … 82 more files in changeset.
Initial steps towards a 2-stage dependency cache

This commit introduces the infrastructure required to get a 2-stage

dependency cache, consisting of a read-only, shareable cache and

a read-write local mutable cache.

The read-only cache would typically be mounted on Docker images.

Only infrastructure, no tests yet.

    • -4
    • +4
    ./DefaultMavenArtifactRepositoryTest.groovy
  1. … 82 more files in changeset.
Initial steps towards a 2-stage dependency cache

This commit introduces the infrastructure required to get a 2-stage

dependency cache, consisting of a read-only, shareable cache and

a read-write local mutable cache.

The read-only cache would typically be mounted on Docker images.

Only infrastructure, no tests yet.

    • -4
    • +4
    ./DefaultMavenArtifactRepositoryTest.groovy
  1. … 82 more files in changeset.
Initial steps towards a 2-stage dependency cache

This commit introduces the infrastructure required to get a 2-stage

dependency cache, consisting of a read-only, shareable cache and

a read-write local mutable cache.

The read-only cache would typically be mounted on Docker images.

Only infrastructure, no tests yet.

    • -4
    • +4
    ./DefaultMavenArtifactRepositoryTest.groovy
  1. … 82 more files in changeset.
Initial steps towards a 2-stage dependency cache

This commit introduces the infrastructure required to get a 2-stage

dependency cache, consisting of a read-only, shareable cache and

a read-write local mutable cache.

The read-only cache would typically be mounted on Docker images.

Only infrastructure, no tests yet.

    • -4
    • +4
    ./DefaultMavenArtifactRepositoryTest.groovy
  1. … 82 more files in changeset.
Initial steps towards a 2-stage dependency cache

This commit introduces the infrastructure required to get a 2-stage

dependency cache, consisting of a read-only, shareable cache and

a read-write local mutable cache.

The read-only cache would typically be mounted on Docker images.

Only infrastructure, no tests yet.

    • -4
    • +4
    ./DefaultMavenArtifactRepositoryTest.groovy
  1. … 82 more files in changeset.
Initial steps towards a 2-stage dependency cache

This commit introduces the infrastructure required to get a 2-stage

dependency cache, consisting of a read-only, shareable cache and

a read-write local mutable cache.

The read-only cache would typically be mounted on Docker images.

Only infrastructure, no tests yet.

    • -4
    • +4
    ./DefaultMavenArtifactRepositoryTest.groovy
  1. … 82 more files in changeset.
Initial steps towards a 2-stage dependency cache

This commit introduces the infrastructure required to get a 2-stage

dependency cache, consisting of a read-only, shareable cache and

a read-write local mutable cache.

The read-only cache would typically be mounted on Docker images.

Only infrastructure, no tests yet.

    • -4
    • +4
    ./DefaultMavenArtifactRepositoryTest.groovy
  1. … 82 more files in changeset.
Initial steps towards a 2-stage dependency cache

This commit introduces the infrastructure required to get a 2-stage

dependency cache, consisting of a read-only, shareable cache and

a read-write local mutable cache.

The read-only cache would typically be mounted on Docker images.

Only infrastructure, no tests yet.

    • -4
    • +4
    ./DefaultMavenArtifactRepositoryTest.groovy
  1. … 82 more files in changeset.
Initial steps towards a 2-stage dependency cache

This commit introduces the infrastructure required to get a 2-stage

dependency cache, consisting of a read-only, shareable cache and

a read-write local mutable cache.

The read-only cache would typically be mounted on Docker images.

Only infrastructure, no tests yet.

    • -4
    • +4
    ./DefaultMavenArtifactRepositoryTest.groovy
  1. … 82 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.

    • -3
    • +4
    ./DefaultMavenArtifactRepositoryTest.groovy
  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.

    • -3
    • +4
    ./DefaultMavenArtifactRepositoryTest.groovy
  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.

    • -3
    • +4
    ./DefaultMavenArtifactRepositoryTest.groovy
  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.

    • -3
    • +4
    ./DefaultMavenArtifactRepositoryTest.groovy
  1. … 103 more files in changeset.
Repository MetadataSources: add public API to retrieve current state

Signed-off-by: Roberto Perez Alcolea <rperezalcolea@netflix.com>

    • -0
    • +29
    ./DefaultMavenArtifactRepositoryTest.groovy
  1. … 5 more files in changeset.
Fix failing tests from insecure HTTP deprecation changes

    • -1
    • +3
    ./DefaultMavenArtifactRepositoryTest.groovy
  1. … 15 more files in changeset.
Refactor HTTP deprecation logic to use HttpRedirectVerifier

    • -1
    • +1
    ./DefaultMavenArtifactRepositoryTest.groovy
  1. … 60 more files in changeset.
Merge branch 'master' into feature/JLL/depricate_http_download_dependencies

* master: (724 commits)

Highlight Gradle Module Metadata support as feature of the release

Add note about configurations deprecations

Increase DaemonErrorFeedbackCrossVersionSpec timeout

Recognize contributor

recognize contributor

Publish 5.6-20190819230034+0000

Remove no longer necessary instant execution codecs for `EnumSet` and `EnumMap`

Improve instant execution support for Java serialization

Polish `BeanPropertyReader.kt`

Polish `BeanCodecTest`

Polish `Codec.kt`

Introduce `SerializableWriteObjectCodec`

Polish `ClosureCodec`

Prepare `BindingsBackedCodec` to accept multiple encodings for the same binding

Simplify `BindingsBackedCodec` usage

Polish `BindingsBackedCodec`

Polish `LoadDirectoryTest`

Remove unused `SerializationFixture` class

Use latest Scan plugin 2.4.1-rc-1

Move Play plugins retirement to 7.0 for now

...

    • -1
    • +1
    ./DefaultMavenArtifactRepositoryTest.groovy
  1. … 21 more files in changeset.
Remove special repository default behavior with GRADLE_METADATA flag

The default behavior is now that we look for 'traditional' metadata

first, but find Gradle metadata if a marker is present.

We won't look for anything else if the 'traditional' metadata is not

found. This increases performance for the cases where one repository

is asked for many modules it does not contain.

Users can opt into different behavior using `gradleMetadata()` or

`artifact()` when defining their repositories.

    • -1
    • +1
    ./DefaultMavenArtifactRepositoryTest.groovy
  1. … 9 more files in changeset.
Remove special repository default behavior with GRADLE_METADATA flag

The default behavior is now that we look for 'traditional' metadata

first, but find Gradle metadata if a marker is present.

We won't look for anything else if the 'traditional' metadata is not

found. This increases performance for the cases where one repository

is asked for many modules it does not contain.

Users can opt into different behavior using `gradleMetadata()` or

`artifact()` when defining their repositories.

    • -1
    • +1
    ./DefaultMavenArtifactRepositoryTest.groovy
  1. … 10 more files in changeset.
Remove special repository default behavior with GRADLE_METADATA flag

The default behavior is now that we look for 'traditional' metadata

first, but find Gradle metadata if a marker is present.

We won't look for anything else if the 'traditional' metadata is not

found. This increases performance for the cases where one repository

is asked for many modules it does not contain.

Users can opt into different behavior using `gradleMetadata()` or

`artifact()` when defining their repositories.

    • -1
    • +1
    ./DefaultMavenArtifactRepositoryTest.groovy
  1. … 10 more files in changeset.
Remove special repository default behavior with GRADLE_METADATA flag

The default behavior is now that we look for 'traditional' metadata

first, but find Gradle metadata if a marker is present.

We won't look for anything else if the 'traditional' metadata is not

found. This increases performance for the cases where one repository

is asked for many modules it does not contain.

Users can opt into different behavior using `gradleMetadata()` or

`artifact()` when defining their repositories.

    • -1
    • +1
    ./DefaultMavenArtifactRepositoryTest.groovy
  1. … 10 more files in changeset.
Remove special repository default behavior with GRADLE_METADATA flag

The default behavior is now that we look for 'traditional' metadata

first, but find Gradle metadata if a marker is present.

We won't look for anything else if the 'traditional' metadata is not

found. This increases performance for the cases where one repository

is asked for many modules it does not contain.

Users can opt into different behavior using `gradleMetadata()` or

`artifact()` when defining their repositories.

    • -1
    • +1
    ./DefaultMavenArtifactRepositoryTest.groovy
  1. … 9 more files in changeset.
Revert "Revert "Merge remote-tracking branch 'origin/sg/merges/pr-9419'""

This reverts commit 0625bc7420e55e87730673231af6ad45dd04f47a.

    • -9
    • +9
    ./DefaultMavenArtifactRepositoryTest.groovy
  1. … 90 more files in changeset.