Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Use the dependency artifacts of all selectors for override metadata

Later in the resolution, we already combine all artifacts defined

as 'dependency artifacts' on incoming edges.

If a component does not have metadata, we also need to consider all

this information early when we look for an artifact (instead of a

metadata file).

    • -2
    • +2
    ./DefaultComponentOverrideMetadata.java
  1. … 9 more files in changeset.
Reuse one object for empty ComponentOverrideMetadata

    • -2
    • +4
    ./DefaultComponentOverrideMetadata.java
  1. … 3 more files in changeset.
Revert "Revert "Merge branch 'release'""

This reverts commit 67b8bb8f18f854f45a2f5ec52cc9c8a25981e2f2.

This restores the merge attempt from earlier.

  1. … 66 more files in changeset.
Revert "Merge branch 'release'"

This reverts commit c7fdc455dcb9a8016af0ae9bc8b4c43fde1e2d06, reversing

changes made to 9f70d52b74dbc8c71381781b6c155474031b3cf8.

The changes need a wrapper as there are API changes. Reverting for now.

  1. … 66 more files in changeset.
Fix AttributeConfigurationSelector to return the filtered result 2/2

Same as 3255f1d for different code path.

  1. … 1 more file in changeset.
Fix AttributeConfigurationSelector to return the filtered result 2/2

Same as 3255f1d for different code path.

  1. … 1 more file in changeset.
Rename inheritStrictVersions() -> endorseStrictVersions() (#10755)

This name change more clearly communicates the semantics of the

feature from a users point of view.

This commit also removes all mentions of 'inheriting' AND 'forSubgraph'.

There have been some leftovers in documentation/comments that

would have been misleading in the future. To make sure we catch all,

this also updates all variable/method/package names.

    • -10
    • +10
    ./LocalComponentDependencyMetadata.java
  1. … 69 more files in changeset.
Rename inheritStrictVersions() -> endorseStrictVersions()

This is more clearly communicating the semantics of the feature

from a users point of view.

The commit also removes all mentions of 'inheriting' AND 'forSubgraph'.

There have been some leftovers in documentation/comments that

will be misleading in the future. To make sure we catch all,

I also updated all variable/method/package names.

    • -10
    • +10
    ./LocalComponentDependencyMetadata.java
  1. … 69 more files in changeset.
Rename inheritStrictVersions() -> endorseStrictVersions()

This is more clearly communicating the semantics of the feature

from a users point of view.

The commit also removes all mentions of 'inheriting' AND 'forSubgraph'.

There have been some leftovers in documentation/comments that

will be misleading in the future. To make sure we catch all,

I also updated all variable/method/package names.

    • -10
    • +10
    ./LocalComponentDependencyMetadata.java
  1. … 69 more files in changeset.
Rename inheritStrictVersions() -> endorseStrictVersions()

This is more clearly communicating the semantics of the feature

from a users point of view.

The commit also removes all mentions of 'inheriting' AND 'forSubgraph'.

There have been some leftovers in documentation/comments that

will be misleading in the future. To make sure we catch all,

I also updated all variable/method/package names.

    • -10
    • +10
    ./LocalComponentDependencyMetadata.java
  1. … 69 more files in changeset.
Support variant and file derivation in realized metadata

This required a couple of changes:

- artifacts are now always explicitly serialized for each configuration

- variant derivation is implemented for variants and for configurations

in maven (derived variants) and ivy

- If a ivy module has configurations (variants) that have been added by

a rule, the realized version uses this information to opt-into

variant aware resolution

  1. … 15 more files in changeset.
Support variant and file derivation in realized metadata

This required a couple of changes:

- artifacts are now always explicitly serialized for each configuration

- variant derivation is implemented for variants and for configurations

in maven (derived variants) and ivy

- If a ivy module has configurations (variants) that have been added by

a rule, the realized version uses this information to opt-into

variant aware resolution

  1. … 12 more files in changeset.
Make evaluation of base variant rules lazy

  1. … 6 more files in changeset.
Make evaluation of base variant rules lazy

  1. … 6 more files in changeset.
Add removeAllFiles() to variant files modification API

Files from an existing 'base' are now also transferred to the new

variant (but can then be removed with removeAllFiles()). This makes:

- The behavior more consistent (before everything was transferred

*except* for the files)

- The 'enrich plain ivy with variants' use case better as you do not

manually have to re-add the files that are already in the configuration

metadata

    • -1
    • +1
    ./DefaultSelectedByVariantMatchingConfigurationMetadata.java
    • -1
    • +2
    ./DefaultSelectedByVariantMatchingLocalConfigurationMetadata.java
  1. … 11 more files in changeset.
Add removeAllFiles() to variant files modification API

Files from an existing 'base' are now also transferred to the new

variant (but can then be removed with removeAllFiles()). This makes:

- The behavior more consistent (before everything was transferred

*except* for the files)

- The 'enrich plain ivy with variants' use case better as you do not

manually have to re-add the files that are already in the configuration

metadata

    • -1
    • +1
    ./DefaultSelectedByVariantMatchingConfigurationMetadata.java
    • -1
    • +2
    ./DefaultSelectedByVariantMatchingLocalConfigurationMetadata.java
  1. … 9 more files in changeset.
Add removeAllFiles() to variant files modification API

Files from an existing 'base' are now also transferred to the new

variant (but can then be removed with removeAllFiles()). This makes:

- The behavior more consistent (before everything was transferred

*except* for the files)

- The 'enrich plain ivy with variants' use case better as you do not

manually have to re-add the files that are already in the configuration

metadata

    • -1
    • +1
    ./DefaultSelectedByVariantMatchingConfigurationMetadata.java
    • -1
    • +2
    ./DefaultSelectedByVariantMatchingLocalConfigurationMetadata.java
  1. … 11 more files in changeset.
Only keep artifacts from pom if the file path is unambiguous

If the packaging indicated in a pom is not in the list of 'known

jar packagings', we assume that the artifact could have the extension

indicated by the packaging. We first test if that artifact exists

with a HEAD request, and only if it does not, we go for the 'jar'

artifact.

Since using a variant file rule disables this mechanism, we remove

such ambiguous artifacts from the modified artifact list to give users

the chance to explicitly state which artifact to expect in the rule

they add anyway.

  1. … 2 more files in changeset.
Only keep artifacts from pom if the file path is unambiguous

If the packaging indicated in a pom is not in the list of 'known

jar packagings', we assume that the artifact could have the extension

indicated by the packaging. We first test if that artifact exists

with a HEAD request, and only if it does not, we go for the 'jar'

artifact.

Since using a variant file rule disables this mechanism, we remove

such ambiguous artifacts from the modified artifact list to give users

the chance to explicitly state which artifact to expect in the rule

they add anyway.

  1. … 2 more files in changeset.
Allow variant matching opt-in for ivy through component metadata rules

  1. … 6 more files in changeset.
Allow variant matching opt-in for ivy through component metadata rules

  1. … 6 more files in changeset.
Allow variant matching opt-in for ivy through component metadata rules

  1. … 13 more files in changeset.
Allow variant matching opt-in for ivy through component metadata rules

  1. … 16 more files in changeset.
Allow variant matching opt-in for ivy through component metadata rules

  1. … 18 more files in changeset.
Allow variant matching opt-in for ivy through component metadata rules

  1. … 18 more files in changeset.
Let resolved variants remember if they were derived

    • -0
    • +5
    ./DefaultSelectedByVariantMatchingConfigurationMetadata.java
  1. … 8 more files in changeset.
Let resolved variants remember if they were derived

    • -0
    • +5
    ./DefaultSelectedByVariantMatchingConfigurationMetadata.java
  1. … 8 more files in changeset.
Let resolved variants remember if they were derived

    • -0
    • +5
    ./DefaultSelectedByVariantMatchingConfigurationMetadata.java
  1. … 8 more files in changeset.
Let resolved variants remember if they were derived

    • -0
    • +5
    ./DefaultSelectedByVariantMatchingConfigurationMetadata.java
  1. … 8 more files in changeset.
Let resolved variants remember if they were derived

    • -0
    • +5
    ./DefaultSelectedByVariantMatchingConfigurationMetadata.java
  1. … 8 more files in changeset.