DefaultMavenLocalRepositoryTest.groovy

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Fix failing tests from insecure HTTP deprecation changes

    • -19
    • +30
    ./DefaultMavenLocalRepositoryTest.groovy
  1. … 5 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
    • +0
    ./DefaultMavenLocalRepositoryTest.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
    • +0
    ./DefaultMavenLocalRepositoryTest.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
    • +0
    ./DefaultMavenLocalRepositoryTest.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
    • +0
    ./DefaultMavenLocalRepositoryTest.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
    • +0
    ./DefaultMavenLocalRepositoryTest.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
    • +0
    ./DefaultMavenLocalRepositoryTest.groovy
  1. … 9 more files in changeset.
Revert "Revert "Merge remote-tracking branch 'origin/sg/merges/pr-9419'""

This reverts commit 0625bc7420e55e87730673231af6ad45dd04f47a.

    • -4
    • +3
    ./DefaultMavenLocalRepositoryTest.groovy
  1. … 90 more files in changeset.
Move validation of secure URLs closer to repository use

    • -14
    • +16
    ./DefaultMavenLocalRepositoryTest.groovy
  1. … 22 more files in changeset.
Move validation of secure URLs closer to repository use

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

This reverts commit 0625bc7420e55e87730673231af6ad45dd04f47a.

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

This reverts commit 2f79026f5e127a8175e25844522237615b19ed52 because of a performance regression,

reversing changes made to 7f1e66079ce629ecde3e09e549e9796ab85761dc.

    • -3
    • +4
    ./DefaultMavenLocalRepositoryTest.groovy
  1. … 90 more files in changeset.
Merge branch 'master' into deprecate_http_download

* master: (225 commits)

Document the purpose of PublicApi.kt

Mention Eclipse test sources as a potential breaking change in the upgrade notes.

Fixed managed property generation for `Property<T>` types where `T` is a parameterized type.

Update library/language versions used by build-init templates.

Remove the instant execution cache file when there is a failure writing to the cache file.

Disallow references to `ConfigurationContainer` from tasks serialized to the instant execution cache.

Recognize contributor

Publish 5.5-20190620010535+0000

Fix small typo in the feature variants chapter of the user guide

Rebaseline instant-execution performance tests

Refine MethodCodec

Polish task actions test

Polish BeanSchema

Temporarily ignore instant execution performance tests

Refine ClassLoaderCacheInternal

Tidy up DefaultInstantExecution & DefaultClassLoaderCache

Add some coverage for captured task actions

Dehydrate Closure and fix BeanSchema for task actions

Add MethodCodec for serializing StandardTaskAction

Let BeanSchema include AbstractTask.actions

...

Signed-off-by: Jonathan Leitschuh <Jonathan.Leitschuh@gradle.com>

    • -2
    • +2
    ./DefaultMavenLocalRepositoryTest.groovy
  1. … 14 more files in changeset.
Replace another usage of the `NamedObjectInstantiator` singleton with an injected service.

    • -3
    • +3
    ./DefaultMavenLocalRepositoryTest.groovy
  1. … 30 more files in changeset.
Replace another usage of the `NamedObjectInstantiator` singleton with an injected service.

    • -3
    • +3
    ./DefaultMavenLocalRepositoryTest.groovy
  1. … 32 more files in changeset.
Replace another usage of the `NamedObjectInstantiator` singleton with an injected service.

    • -3
    • +3
    ./DefaultMavenLocalRepositoryTest.groovy
  1. … 32 more files in changeset.
Replace another usage of the `NamedObjectInstantiator` singleton with an injected service.

    • -3
    • +3
    ./DefaultMavenLocalRepositoryTest.groovy
  1. … 32 more files in changeset.
Resolve additional failing tests

Signed-off-by: Jonathan Leitschuh <Jonathan.Leitschuh@gmail.com>

    • -5
    • +4
    ./DefaultMavenLocalRepositoryTest.groovy
  1. … 8 more files in changeset.
Rename writer/parser classes for consistency

    • -2
    • +2
    ./DefaultMavenLocalRepositoryTest.groovy
  1. … 21 more files in changeset.
Split off value snapshotting and attributes related methods of TestUtil

    • -2
    • +4
    ./DefaultMavenLocalRepositoryTest.groovy
  1. … 64 more files in changeset.
Support Named attributes in component metadata rule caching

The Named limitation is ok as it was imposed by making

ComponentMetadataRule isolatable already.

This requires the ability to inject the ObjectFactory in rules

    • -3
    • +3
    ./DefaultMavenLocalRepositoryTest.groovy
  1. … 22 more files in changeset.
Create and wire in a ComponentMetadataRuleExecutor

This enables ComponentMetadataRule execution to be cached

Update the CrossBuildCachingRuleExecutor to work with a set of rule

instead of a single one. This means we cache or miss on a chain of rules

instead of single rules.

Fixes #5526

    • -0
    • +2
    ./DefaultMavenLocalRepositoryTest.groovy
  1. … 32 more files in changeset.
Enforce isolation of ComponentMetadataRule

This means that passed in parameters must be snapshotable as defined by

the ValueSnapshotter

Added support for Attribute to ValueSnapshotter

    • -1
    • +2
    ./DefaultMavenLocalRepositoryTest.groovy
  1. … 53 more files in changeset.
Rename 'experimental features' to 'feature previews'

The idea behind this is that we have a set of feature previews rather

than one cryptic experimental flag.

A feature preview collects a set of related functionality (e.g.

everything related to gradle metadata) that changes existing behavior

and thus could potentially break existing builds. The preview options

will be removed with the next major release (currently 5.0) and the new

behaviour will then become the default.

Signed-off-by: Jendrik Johannes <jendrik@gradle.com>

    • -2
    • +2
    ./DefaultMavenLocalRepositoryTest.groovy
  1. … 45 more files in changeset.
Adjust tests to use the new experimental feature option

Signed-off-by: Jendrik Johannes <jendrik@gradle.com>

    • -2
    • +1
    ./DefaultMavenLocalRepositoryTest.groovy
  1. … 23 more files in changeset.
Provide additional services to constructor calls in tests

Signed-off-by: Jendrik Johannes <jendrik@gradle.com>

    • -1
    • +1
    ./DefaultMavenLocalRepositoryTest.groovy
  1. … 14 more files in changeset.
Initial implementation of component metadata rules allowing modification of variant attributes

This commit introduces metadata rules that support modification of variant attributes. Variant attributes

are specific to each variant and can be found in module metadata. Those are NOT component level attributes,

which could be used during dependency resolution. This will be added in a subsequent commit.

    • -1
    • +1
    ./DefaultMavenLocalRepositoryTest.groovy
  1. … 49 more files in changeset.
Instantiate mutable Maven metadata through dependency injecting instantiator

This commit prepares the ability to inject services into mutable Maven metadata. This will be

required to inject the immutable attributes factory, as well as the object instantiator and

possibly other services to the immutable Maven resolve metadata. This commit reduces the

number of constructors of `DefaultMavenModuleResolveMetadata`, to make it easier to maintain.

Some tests still create mutable module resolve metadata directly. Ideally, they should also

use the factory.

    • -2
    • +15
    ./DefaultMavenLocalRepositoryTest.groovy
  1. … 19 more files in changeset.
Introduce `MetadataSource` implementations

This commit extract the metadata-specific behaviour of `ExternalResourceResolver` subtypes

into separate `MetadataSource` implementations, and refactors `ExternalResourceResolver` to use them.

Each registered `MetadataSource` is attempted in sequence. If metadata is found using an earlier

source, the later sources are not attempted. The default sequence is:

- Gradle metadata (if experimentalFeatures enabled), then

- Ivy (or Maven) metadata, then

- Artifact

This is a pure refactor: no change to behaviour results from this change.

    • -4
    • +2
    ./DefaultMavenLocalRepositoryTest.groovy
  1. … 36 more files in changeset.
Use ExperimentalFeatures flag to enable consumption of module metadata

TODO: convert the remaining uses of `ComponentAwareRepository`

    • -1
    • +2
    ./DefaultMavenLocalRepositoryTest.groovy
  1. … 8 more files in changeset.