Gradle

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Clean release notes and welcome message for 5.6

    • -40
    • +1
    /subprojects/docs/src/docs/release/notes.md
Merge remote-tracking branch 'origin/master-test' into release-test

Publish 5.4.1-20190506010034+0000

WIP - documentation.

    • -0
    • +10
    /subprojects/docs/src/docs/release/notes.md
WIP - documentation.

    • -0
    • +10
    /subprojects/docs/src/docs/release/notes.md
Fixes for previous commit.

Fixes for previous commit.

Fixes for previous commit.

Fixes for previous commit.

Fixes for previous commit.

Minor refactoring for readability

Minor refactoring for readability

Compute "hasTransitiveEdges" on the go

Instead of iterating on edges and potentially creating a list,

that we don't need given we only need to know if there's any

transitive edge.

Compute "hasTransitiveEdges" on the go

Instead of iterating on edges and potentially creating a list,

that we don't need given we only need to know if there's any

transitive edge.

Fix failing test

Fix failing test

Sort module selectors

This commit reworks module selectors so that they are sorted

in an order which reduces the cost of module selection. We

make sure to put local (project) selectors first, then we

use selectors from locks (if any).

The next selectors are "latest" version selectors because

even if they are dynamic, they are likely to "win" selection.

Then, exact version selectors are sorted by version descending

, and last we add dynamic version selectors.

  1. … 5 more files in changeset.
Sort module selectors

This commit reworks module selectors so that they are sorted

in an order which reduces the cost of module selection. We

make sure to put local (project) selectors first, then we

use selectors from locks (if any).

The next selectors are "latest" version selectors because

even if they are dynamic, they are likely to "win" selection.

Then, exact version selectors are sorted by version descending

, and last we add dynamic version selectors.

  1. … 5 more files in changeset.
Sort module selectors

This commit reworks module selectors so that they are sorted

in an order which reduces the cost of module selection. We

make sure to put local (project) selectors first, then we

use selectors from locks (if any).

The next selectors are "latest" version selectors because

even if they are dynamic, they are likely to "win" selection.

Then, exact version selectors are sorted by version descending

, and last we add dynamic version selectors.

  1. … 5 more files in changeset.
Sort module selectors

This commit reworks module selectors so that they are sorted

in an order which reduces the cost of module selection. We

make sure to put local (project) selectors first, then we

use selectors from locks (if any).

The next selectors are "latest" version selectors because

even if they are dynamic, they are likely to "win" selection.

Then, exact version selectors are sorted by version descending

, and last we add dynamic version selectors.

  1. … 5 more files in changeset.
Sort module selectors

This commit reworks module selectors so that they are sorted

in an order which reduces the cost of module selection. We

make sure to put local (project) selectors first, then we

use selectors from locks (if any).

The next selectors are "latest" version selectors because

even if they are dynamic, they are likely to "win" selection.

Then, exact version selectors are sorted by version descending

, and last we add dynamic version selectors.

  1. … 5 more files in changeset.
Update released version to latest snapshot

Update version to 5.6

Clean release notes and welcome message for 5.6

    • -40
    • +1
    /subprojects/docs/src/docs/release/notes.md
Merge remote-tracking branch 'origin/master-test' into release-test

Publish 5.4.1-20190505010037+0000

Avoid re-creating selection reason

Selection reasons should be immutable. It wasn't because for forced

platforms we were relying on it to determine if it was forced or

not. This is now changed to use the selectors instead, and we can

cache the selection reason.

Avoid re-creating selection reason

Selection reasons should be immutable. It wasn't because for forced

platforms we were relying on it to determine if it was forced or

not. This is now changed to use the selectors instead, and we can

cache the selection reason.

Optimize selection in case a variant provides the implicit capability

This avoids iterating over capabilities when there's a single capability

and that it is the shadowed, implicit capability.

Optimize selection in case a variant provides the implicit capability

This avoids iterating over capabilities when there's a single capability

and that it is the shadowed, implicit capability.