Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Add clarifying comment about realizing artifact tasks that do not run

    • -0
    • +3
    ./PublishArtifactLocalArtifactMetadata.java
Add clarifying comment about realizing artifact tasks that do not run

    • -0
    • +3
    ./PublishArtifactLocalArtifactMetadata.java
Make task creation parallel save

    • -1
    • +6
    ./PublishArtifactLocalArtifactMetadata.java
Compute the name of PublishArtifactLocalArtifactMetadata lazily

In case where the publish artifact is of type 'LazyPublishArtifact',

this broke the laziness.

    • -2
    • +4
    ./PublishArtifactLocalArtifactMetadata.java
Compute the name of PublishArtifactLocalArtifactMetadata lazily

In case where the publish artifact is of type 'LazyPublishArtifact',

this broke the laziness.

    • -2
    • +4
    ./PublishArtifactLocalArtifactMetadata.java
  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.

    • -2
    • +2
    ./DefaultProjectDependencyMetadata.java
    • -2
    • +2
    ./DslOriginDependencyMetadataWrapper.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.

    • -2
    • +2
    ./DefaultProjectDependencyMetadata.java
    • -2
    • +2
    ./DslOriginDependencyMetadataWrapper.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.

    • -2
    • +2
    ./DefaultProjectDependencyMetadata.java
    • -2
    • +2
    ./DslOriginDependencyMetadataWrapper.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.

    • -2
    • +2
    ./DefaultProjectDependencyMetadata.java
    • -2
    • +2
    ./DslOriginDependencyMetadataWrapper.java
  1. … 69 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. … 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. … 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. … 13 more files in changeset.
Let resolved variants remember if they were derived

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

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

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

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

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

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

  1. … 9 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

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

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

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

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

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

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

  1. … 32 more files in changeset.