userguide

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Force Scala library 2.12 with Zinc

    • -19
    • +0
    ./scala/zincOverride/groovy/build.gradle
    • -19
    • +0
    ./scala/zincOverride/kotlin/build.gradle.kts
    • -1
    • +0
    ./scala/zincOverride/kotlin/settings.gradle.kts
  1. … 3 more files in changeset.
Revert "Revert "Merge branch 'release'""

This reverts commit 67b8bb8f18f854f45a2f5ec52cc9c8a25981e2f2.

This restores the merge attempt from earlier.

  1. … 62 more files in changeset.
Revert "Merge branch 'release'"

This reverts commit c7fdc455dcb9a8016af0ae9bc8b4c43fde1e2d06, reversing

changes made to 9f70d52b74dbc8c71381781b6c155474031b3cf8.

The changes need a wrapper as there are API changes. Reverting for now.

  1. … 62 more files in changeset.
Support variant selection in capability conflict resolution (#10973)

A conflict can also occur between two variants of the same component.

This gives access to the variant name in the selection rule and

evicts nodes that represent the not-selected variant.

  1. … 10 more files in changeset.
Support variant selection in capability conflict resolution

A conflict can also occur between two variants of the same component.

This gives access to the variant name in the selection rule and

evicts nodes that represent the not-selected variant.

  1. … 10 more files in changeset.
Support variant selection in capability conflict resolution

A conflict can also occur between two variants of the same component.

This gives access to the variant name in the selection rule and

evicts nodes that represent the not-selected variant.

  1. … 9 more files in changeset.
Remove unnecessary comment from sample

Enhance cross project publication sample

Added info on how to setup the configuration to share the same

dependencies.

Enhance cross project publication sample

Added info on how to setup the configuration to share the same

dependencies.

Fix result of capabilities conflict

The documentation still used the old message / format

  1. … 2 more files in changeset.
Fix result of capabilities conflict

The documentation still used the old message / format

  1. … 2 more files in changeset.
Add documentation about `failOnXXX` methods

  1. … 3 more files in changeset.
Add documentation about `failOnXXX` methods

  1. … 3 more files in changeset.
Fix tests

Fix tests

Fix samples

Fix samples

Userguide: mention runtime validation and remove runtime property override

  1. … 1 more file in changeset.
Userguide: mention runtime validation and remove runtime property override

  1. … 1 more file in changeset.
Rewrite section on 'excluding dependencies'

  1. … 18 more files in changeset.
Rewrite section on 'excluding dependencies'

  1. … 18 more files in changeset.
Update samples to avoid deprecated APIs

    • -1
    • +1
    ./distribution/kotlin/build.gradle.kts
    • -1
    • +1
    ./tutorial/manifest/groovy/build.gradle
  1. … 3 more files in changeset.
Update samples to avoid deprecated APIs

    • -1
    • +1
    ./distribution/kotlin/build.gradle.kts
    • -2
    • +2
    ./tutorial/manifest/groovy/build.gradle
  1. … 3 more files in changeset.
Avoid more deprecated APIs

    • -2
    • +2
    ./javaLibraryDistribution/kotlin/build.gradle.kts
  1. … 1 more file in changeset.
Put Java Library Plugin forward

Instead of referencing first the Java plugin, the guide now uses the

Java Library plugin directly and clearly states that the Java plugin

should be seen as a technical layer and not something to be applied

explicitly in a build file.

  1. … 1 more file in changeset.
Put Java Library Plugin forward

Instead of referencing first the Java plugin, the guide now uses the

Java Library plugin directly and clearly states that the Java plugin

should be seen as a technical layer and not something to be applied

explicitly in a build file.

  1. … 1 more file in changeset.
Put Java Library Plugin forward

Instead of referencing first the Java plugin, the guide now uses the

Java Library plugin directly and clearly states that the Java plugin

should be seen as a technical layer and not something to be applied

explicitly in a build file.

  1. … 1 more file in changeset.
Suppress remaining deprecation warnings

- most are because of the use of the deprecated Maven plugin

- some are because of the deprecated `force` option in dependency management

- +1: Ratpack plugin used "compile" configuration

    • -0
    • +4
    ./artifacts/maven/publishMavenRepository.sample.conf
    • -0
    • +4
    ./distribution/useDistributionPlugin.sample.conf
  1. … 5 more files in changeset.
Use correct configuratoins instead of deprecated ones

  1. … 1 more file in changeset.
Add missing input/output annotations in samples

  1. … 2 more files in changeset.