Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Make evaluation of base variant rules lazy

    • -1
    • +1
    ./model/AbstractConfigurationMetadata.java
    • -23
    • +3
    ./model/AbstractLazyModuleComponentResolveMetadata.java
    • -1
    • +1
    ./model/AbstractMutableModuleComponentResolveMetadata.java
    • -0
    • +153
    ./model/LazyRuleAwareWithBaseConfigurationMetadata.java
    • -11
    • +3
    ./model/LazyVariantBackedConfigurationMetadata.java
  1. … 2 more files in changeset.
Add a spike implementation of a Homebrew repository, that can locate pre-built libraries in the local Homebrew repository.

    • -1
    • +1
    ./model/AbstractConfigurationMetadata.java
    • -1
    • +1
    ./model/AbstractModuleComponentResolveMetadata.java
  1. … 5 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
    • +5
    ./model/AbstractLazyModuleComponentResolveMetadata.java
    • -5
    • +8
    ./model/LazyVariantBackedConfigurationMetadata.java
  1. … 13 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
    • +5
    ./model/AbstractLazyModuleComponentResolveMetadata.java
    • -5
    • +8
    ./model/LazyVariantBackedConfigurationMetadata.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
    • +5
    ./model/AbstractLazyModuleComponentResolveMetadata.java
    • -5
    • +8
    ./model/LazyVariantBackedConfigurationMetadata.java
  1. … 13 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.

    • -6
    • +16
    ./model/AbstractLazyModuleComponentResolveMetadata.java
  1. … 5 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.

    • -6
    • +16
    ./model/AbstractLazyModuleComponentResolveMetadata.java
  1. … 5 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
    ./model/maven/DefaultMavenModuleResolveMetadata.java
  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
    ./model/maven/DefaultMavenModuleResolveMetadata.java
  1. … 2 more files in changeset.
Derive variants for ivy, if publication matches Java library pattern

    • -0
    • +7
    ./model/ConfigurationBoundExternalDependencyMetadata.java
    • -7
    • +6
    ./model/JavaEcosystemVariantDerivationStrategy.java
    • -0
    • +28
    ./model/ivy/DefaultIvyModuleResolveMetadata.java
    • -4
    • +4
    ./model/maven/DefaultMavenModuleResolveMetadata.java
  1. … 10 more files in changeset.
Fixes

    • -5
    • +2
    ./model/ivy/DefaultIvyModuleResolveMetadata.java
  1. … 2 more files in changeset.
Fixes

    • -13
    • +0
    ./model/ivy/DefaultIvyModuleResolveMetadata.java
  1. … 2 more files in changeset.
Fixes

    • -0
    • +7
    ./model/ConfigurationBoundExternalDependencyMetadata.java
    • -31
    • +1
    ./model/ivy/DefaultIvyModuleResolveMetadata.java
  1. … 7 more files in changeset.
Fixes

    • -5
    • +2
    ./model/ivy/DefaultIvyModuleResolveMetadata.java
  1. … 4 more files in changeset.
Fixes

    • -0
    • +7
    ./model/ConfigurationBoundExternalDependencyMetadata.java
    • -31
    • +1
    ./model/ivy/DefaultIvyModuleResolveMetadata.java
  1. … 28 more files in changeset.
Fixes

    • -0
    • +7
    ./model/ConfigurationBoundExternalDependencyMetadata.java
    • -31
    • +1
    ./model/ivy/DefaultIvyModuleResolveMetadata.java
  1. … 18 more files in changeset.
Fixes

    • -0
    • +7
    ./model/ConfigurationBoundExternalDependencyMetadata.java
    • -31
    • +1
    ./model/ivy/DefaultIvyModuleResolveMetadata.java
  1. … 30 more files in changeset.
Fixes

    • -0
    • +5
    ./model/ConfigurationBoundExternalDependencyMetadata.java
    • -31
    • +1
    ./model/ivy/DefaultIvyModuleResolveMetadata.java
  1. … 4 more files in changeset.
Derive variants for ivy, if publication matches Java library pattern

    • -7
    • +6
    ./model/JavaEcosystemVariantDerivationStrategy.java
    • -0
    • +58
    ./model/ivy/DefaultIvyModuleResolveMetadata.java
    • -4
    • +4
    ./model/maven/DefaultMavenModuleResolveMetadata.java
  1. … 11 more files in changeset.
Allow variant matching opt-in for ivy through component metadata rules

    • -0
    • +27
    ./model/ivy/DefaultIvyModuleResolveMetadata.java
    • -0
    • +27
    ./model/ivy/RealisedIvyModuleResolveMetadata.java
  1. … 6 more files in changeset.
Allow variant matching opt-in for ivy through component metadata rules

    • -0
    • +27
    ./model/ivy/DefaultIvyModuleResolveMetadata.java
    • -0
    • +27
    ./model/ivy/RealisedIvyModuleResolveMetadata.java
  1. … 6 more files in changeset.
Allow variant matching opt-in for ivy through component metadata rules

    • -0
    • +22
    ./model/ivy/DefaultIvyModuleResolveMetadata.java
  1. … 14 more files in changeset.
Allow variant matching opt-in for ivy through component metadata rules

    • -0
    • +27
    ./model/ivy/DefaultIvyModuleResolveMetadata.java
    • -0
    • +27
    ./model/ivy/RealisedIvyModuleResolveMetadata.java
  1. … 16 more files in changeset.
Allow variant matching opt-in for ivy through component metadata rules

    • -0
    • +27
    ./model/ivy/DefaultIvyModuleResolveMetadata.java
    • -0
    • +27
    ./model/ivy/RealisedIvyModuleResolveMetadata.java
  1. … 18 more files in changeset.
Allow variant matching opt-in for ivy through component metadata rules

    • -0
    • +27
    ./model/ivy/DefaultIvyModuleResolveMetadata.java
    • -0
    • +27
    ./model/ivy/RealisedIvyModuleResolveMetadata.java
  1. … 18 more files in changeset.
Realized component variants need to provide all attributes

Since this only affected the certain realized versions of variants, this

only caused incorrect result reporting.

    • -7
    • +78
    ./model/RealisedVariantBackedConfigurationMetadata.java
Realized component variants also need to provide all attributes

Since this only affected the realized versions of variants, which have

already been matched, this should have only caused incorrect result

reporting.

    • -7
    • +78
    ./model/RealisedVariantBackedConfigurationMetadata.java
Let resolved variants remember if they were derived

    • -0
    • +5
    ./model/AbstractConfigurationMetadata.java
    • -0
    • +5
    ./model/AbstractVariantBackedConfigurationMetadata.java
    • -35
    • +19
    ./model/DefaultConfigurationMetadata.java
    • -1
    • +1
    ./model/ivy/DefaultIvyModuleResolveMetadata.java
    • -2
    • +2
    ./model/maven/DefaultMavenModuleResolveMetadata.java
  1. … 5 more files in changeset.
Let resolved variants remember if they were derived

    • -0
    • +5
    ./model/AbstractConfigurationMetadata.java
    • -0
    • +5
    ./model/AbstractVariantBackedConfigurationMetadata.java
    • -35
    • +19
    ./model/DefaultConfigurationMetadata.java
    • -1
    • +1
    ./model/ivy/DefaultIvyModuleResolveMetadata.java
    • -2
    • +2
    ./model/maven/DefaultMavenModuleResolveMetadata.java
  1. … 5 more files in changeset.
Let resolved variants remember if they were derived

    • -0
    • +5
    ./model/AbstractConfigurationMetadata.java
    • -0
    • +5
    ./model/AbstractVariantBackedConfigurationMetadata.java
    • -35
    • +19
    ./model/DefaultConfigurationMetadata.java
    • -1
    • +1
    ./model/ivy/DefaultIvyModuleResolveMetadata.java
    • -2
    • +2
    ./model/maven/DefaultMavenModuleResolveMetadata.java
  1. … 5 more files in changeset.