artifacts

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Always apply all Category disambiguation rules in Java ecosystem

Before, parts of the platform disambiguation were only done when

using the 'java-platform' plugin. However, consumers using other

Java plugins may also require all rules (see #11091)

  1. … 5 more files in changeset.
Remove derived enforced-platform variants

Instead, implement them with strict versions for external modules.

    • -0
    • +1
    ./dependencies/DefaultProjectDependency.java
  1. … 19 more files in changeset.
Remove derived enforced-platform variants

Instead, implement them with strict versions for external modules.

    • -0
    • +1
    ./dependencies/DefaultProjectDependency.java
  1. … 19 more files in changeset.
Remove derived enforced-platform variants

Instead, implement them with strict versions for external modules.

    • -0
    • +1
    ./dependencies/DefaultProjectDependency.java
  1. … 19 more files in changeset.
Remove derived enforced-platform variants

Instead, implement them with strict versions for external modules.

    • -0
    • +1
    ./dependencies/DefaultProjectDependency.java
  1. … 13 more files in changeset.
Remove derived enforced-platform variants

Instead, implement them with strict versions for external modules.

    • -0
    • +1
    ./dependencies/DefaultProjectDependency.java
  1. … 19 more files in changeset.
Remove derived enforced-platform variants

Instead, implement them with strict versions for external modules.

    • -0
    • +1
    ./dependencies/DefaultProjectDependency.java
  1. … 19 more files in changeset.
Add disambiguation rule for platforms

  1. … 1 more file in changeset.
Track 'changing' and 'client module' information for override metadata

Although these are edge cases, it leads to more consistency and makes

the behavior less dependent on order which may change unexpectedly

through internal optimisations.

    • -0
    • +1
    ./dependencies/AbstractModuleDependency.java
  1. … 7 more files in changeset.
A client module defining dependency declaration is always different

    • -0
    • +4
    ./dependencies/AbstractModuleDependency.java
Use a linked hash set for dependency artifacts

The order can make a difference in repository selection, when

checking if an artifact-only-component containing the artifacts

exists in a repository. In absence of a metadata file, we initially test

for the existence of one artifact to decide if a repository contains

the corresponding artifact-only-component. This is always the first

artifact in the set (which is internally converted into a list).

This change makes sure that the first artifact is always the same

for a build that does not change.

    • -3
    • +3
    ./dependencies/AbstractModuleDependency.java
Use a linked hash set for dependency artifacts

The order can make a difference in repository selection, when

checking if an artifact-only-component containing the artifacts

exists in a repository. In absence of a metadata file, we initially test

for the existence of one artifact to decide if a repository contains

the corresponding artifact-only-component. This is always the first

artifact in the set (which is internally converted into a list).

This change makes sure that the first artifact is always the same

for a build that does not change.

    • -3
    • +3
    ./dependencies/AbstractModuleDependency.java
Use a linked hash set for dependency artifacts

The order can make a difference in repository selection, when

checking if an artifact-only-component containing the artifacts

exists in a repository. In absence of a metadata file, we initially test

for the existence of one artifact to decide if a repository contains

the corresponding artifact-only-component. This is always the first

artifact in the set (which is internally converted into a list).

This change makes sure that the first artifact is always the same

for a build that does not change.

    • -3
    • +3
    ./dependencies/AbstractModuleDependency.java
Use a linked hash set for dependency artifacts

The order can make a difference in repository selection, when

checking if an artifact-only-component containing the artifacts

exists in a repository. In absence of a metadata file, we initially test

for the existence of one artifact to decide if a repository contains

the corresponding artifact-only-component. This is always the first

artifact in the set (which is internally converted into a list).

This change makes sure that the first artifact is always the same

for a build that does not change.

    • -3
    • +3
    ./dependencies/AbstractModuleDependency.java
Use a linked hash set for dependency artifacts

The order can make a difference in repository selection, when

checking if an artifact-only-component containing the artifacts

exists in a repository. In absence of a metadata file, we initially test

for the existence of one artifact to decide if a repository contains

the corresponding artifact-only-component. This is always the first

artifact in the set (which is internally converted into a list).

This change makes sure that the first artifact is always the same

for a build that does not change.

    • -3
    • +3
    ./dependencies/AbstractModuleDependency.java
Add nags for deprecated AbstractArchiveTask methods

    • -9
    • +11
    ./publish/ArchivePublishArtifact.java
  1. … 1 more file in changeset.
Add nags for deprecated AbstractArchiveTask methods

    • -9
    • +11
    ./publish/ArchivePublishArtifact.java
  1. … 1 more file in changeset.
Add nags for deprecated AbstractArchiveTask methods

    • -9
    • +11
    ./publish/ArchivePublishArtifact.java
  1. … 1 more file in changeset.
Add nags for deprecated AbstractArchiveTask methods

    • -9
    • +11
    ./publish/ArchivePublishArtifact.java
  1. … 1 more file in changeset.
Revert "Category.DOCUMENTATION is compatible with other category types"

This reverts commit 92c3b4bddc0620f9300493b5f035f4bb98aacf5d.

Category.DOCUMENTATION is compatible with other category types

If one requests documentation, we want to be lenient. That is,

if a publication does not contain any documentation, we don't want

to fail. Instead, we now just return what we have (i.e. the main

artifact) which can also be used for documentation purpose in

the absence of other documentation. E.g. an IDE can de-compile

the bytecode if the source code is missing.

This change is also needed to make local matching work. Since

the documentation variants are secondary variants to a primary

LIBRARY variant, the matching would fail on the incompatible

primary variant before even considering the secondary variants

for selection.

Category.DOCUMENTATION is compatible with other category types

If one requests documentation, we want to be lenient. That is,

if a publication does not contain any documentation, we don't want

to fail. Instead, we now just return what we have (i.e. the main

artifact) which can also be used for documentation purpose in

the absence of other documentation. E.g. an IDE can de-compile

the bytecode if the source code is missing.

This change is also needed to make local matching work. Since

the documentation variants are secondary variants to a primary

LIBRARY variant, the matching would fail on the incompatible

primary variant before even considering the secondary variants

for selection.

Category.DOCUMENTATION is compatible with other category types

If one requests documentation, we want to be lenient. That is,

if a publication does not contain any documentation, we don't want

to fail. Instead, we now just return what we have (i.e. the main

artifact) which can also be used for documentation purpose in

the absence of other documentation. E.g. an IDE can de-compile

the bytecode if the source code is missing.

This change is also needed to make local matching work. Since

the documentation variants are secondary variants to a primary

LIBRARY variant, the matching would fail on the incompatible

primary variant before even considering the secondary variants

for selection.

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.

    • -7
    • +7
    ./dependencies/AbstractModuleDependency.java
  1. … 70 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.

    • -7
    • +7
    ./dependencies/AbstractModuleDependency.java
  1. … 70 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.

    • -7
    • +7
    ./dependencies/AbstractModuleDependency.java
  1. … 70 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.

    • -7
    • +7
    ./dependencies/AbstractModuleDependency.java
  1. … 70 more files in changeset.
Change exception to InvalidUserCodeException

Issue #10532

    • -4
    • +5
    ./dependencies/AbstractModuleDependency.java
  1. … 1 more file in changeset.
Change exception to InvalidUserCodeException

Issue #10532

    • -4
    • +5
    ./dependencies/AbstractModuleDependency.java
  1. … 1 more file in changeset.
Change exception to InvalidUserCodeException

Issue #10532

    • -4
    • +5
    ./dependencies/AbstractModuleDependency.java
  1. … 1 more file in changeset.