Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
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.
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.
Do not drop variant attributes in results based on maven artifacts

FixedComponentArtifacts dropped the variant attributes (stored in

ConfigurationMetadata) for no clear reason. Because of this, the

attributes in the resolve result differed depending on whether the

variant was constructed from pom or GMM.

This is only affecting the attributes reported in the result. During

matching, which happens earlier, all attributes were already considered.

  1. … 17 more files in changeset.
Do not drop variant attributes in results based on maven artifacts

FixedComponentArtifacts dropped the variant attributes (stored in

ConfigurationMetadata) for no clear reason. Because of this, the

attributes in the resolve result differed depending on whether the

variant was constructed from pom or GMM.

This is only affecting the attributes reported in the result. During

matching, which happens earlier, all attributes were already considered.

  1. … 17 more files in changeset.
Do not drop variant attributes in results based on maven artifacts

FixedComponentArtifacts dropped the variant attributes (stored in

ConfigurationMetadata) for no clear reason. Because of this, the

attributes in the resolve result differed depending on whether the

variant was constructed from pom or GMM.

This is only affecting the attributes reported in the result. During

matching, which happens earlier, all attributes were already considered.

  1. … 17 more files in changeset.
Do not drop variant attributes in results based on maven artifacts

FixedComponentArtifacts dropped the variant attributes (stored in

ConfigurationMetadata) for no clear reason. Because of this, the

attributes in the resolve result differed depending on whether the

variant was constructed from pom or GMM.

This is only affecting the attributes reported in the result. During

matching, which happens earlier, all attributes were already considered.

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

    • -0
    • +5
    ./DefaultSelectedByVariantMatchingConfigurationMetadata.java
  1. … 5 more files in changeset.
Add support for adding variants and files to component metadata rules

  1. … 28 more files in changeset.
Add support for adding variants and files to component metadata rules

  1. … 28 more files in changeset.
Add support for adding variants and files to component metadata rules

    • -0
    • +27
    ./ModuleConfigurationMetadata.java
  1. … 21 more files in changeset.
Add support for adding variants and files to component metadata rules

  1. … 22 more files in changeset.
Add support for adding variants and files to component metadata rules

  1. … 12 more files in changeset.
Add support for adding variants and files to component metadata rules

  1. … 27 more files in changeset.
Add support for adding variants and files to component metadata rules

  1. … 28 more files in changeset.
Add support for adding variants and files to component metadata rules

  1. … 12 more files in changeset.
Add support for adding variants and files to component metadata rules

  1. … 28 more files in changeset.
Add support for adding variants and files to component metadata rules

  1. … 25 more files in changeset.