VariantFilesMetadataRulesIntegrationTest.groovy

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
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

    • -5
    • +5
    ./VariantFilesMetadataRulesIntegrationTest.groovy
  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

    • -5
    • +7
    ./VariantFilesMetadataRulesIntegrationTest.groovy
  1. … 12 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

    • -8
    • +4
    ./VariantFilesMetadataRulesIntegrationTest.groovy
  1. … 14 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

    • -8
    • +4
    ./VariantFilesMetadataRulesIntegrationTest.groovy
  1. … 12 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

    • -8
    • +4
    ./VariantFilesMetadataRulesIntegrationTest.groovy
  1. … 14 more files in changeset.
Add API method to ad a variant without base

Also extend documentation about 'base' and throw errors if a

non-existing base is defined.

    • -1
    • +47
    ./VariantFilesMetadataRulesIntegrationTest.groovy
  1. … 6 more files in changeset.
Add API method to ad a variant without base

Also extend documentation about 'base' and throw errors if a

non-existing base is defined.

    • -1
    • +47
    ./VariantFilesMetadataRulesIntegrationTest.groovy
  1. … 6 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.

    • -0
    • +67
    ./VariantFilesMetadataRulesIntegrationTest.groovy
  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.

    • -0
    • +67
    ./VariantFilesMetadataRulesIntegrationTest.groovy
  1. … 2 more files in changeset.
Add support for adding variants and files to component metadata rules

    • -0
    • +348
    ./VariantFilesMetadataRulesIntegrationTest.groovy
  1. … 32 more files in changeset.
Add support for adding variants and files to component metadata rules

    • -0
    • +137
    ./VariantFilesMetadataRulesIntegrationTest.groovy
  1. … 32 more files in changeset.
Add support for adding variants and files to component metadata rules

    • -0
    • +111
    ./VariantFilesMetadataRulesIntegrationTest.groovy
  1. … 31 more files in changeset.
Add support for adding variants and files to component metadata rules

    • -0
    • +394
    ./VariantFilesMetadataRulesIntegrationTest.groovy
  1. … 32 more files in changeset.
Add support for adding variants and files to component metadata rules

    • -0
    • +137
    ./VariantFilesMetadataRulesIntegrationTest.groovy
  1. … 32 more files in changeset.
Add support for adding variants and files to component metadata rules

    • -0
    • +394
    ./VariantFilesMetadataRulesIntegrationTest.groovy
  1. … 29 more files in changeset.