snippets

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Make it possible to use an ecosystem describer in more cases

Before this commit the describer would only be used if the same set of attributes

was found. This means that if the consumer added, or removed, one attribute, we

would lose the benefit of better user error messages. With this change, we try

to find the _best matching_ describer, if any.

  1. … 20 more files in changeset.
Make it possible to use an ecosystem describer in more cases

Before this commit the describer would only be used if the same set of attributes

was found. This means that if the consumer added, or removed, one attribute, we

would lose the benefit of better user error messages. With this change, we try

to find the _best matching_ describer, if any.

  1. … 19 more files in changeset.
Update to latest commons lang 3 release

This is a quick fix: the test should not check the dynamic version.

Improve error reporting for the Java ecosystem

This commit introduces improved error messages for the Java ecosystem

in case of variant matching errors.

  1. … 26 more files in changeset.
Improve variant matching error messages

Error messages prove to be difficult to interpret from a user point of

view. This commit tries to improve the situation by doing a couple of

things:

1. describing more clearly what the consumer is asking for. This includes,

when possible (currently only in the Java ecosystem), interpreting the

consumer attributes as a human-readable description, instead of a raw

list of attributes.

2. giving more context when possible. In particular, sometimes we fail

with an ambiguous variant error selection, but we only list the remaining

candidates, not listing the ones which were actually discarded during

selection. This proved to be particularly complex to debug from various

users (plugin authors and end-users).

  1. … 46 more files in changeset.
Improve variant matching error messages

Error messages prove to be difficult to interpret from a user point of

view. This commit tries to improve the situation by doing a couple of

things:

1. describing more clearly what the consumer is asking for. This includes,

when possible (currently only in the Java ecosystem), interpreting the

consumer attributes as a human-readable description, instead of a raw

list of attributes.

2. giving more context when possible. In particular, sometimes we fail

with an ambiguous variant error selection, but we only list the remaining

candidates, not listing the ones which were actually discarded during

selection. This proved to be particularly complex to debug from various

users (plugin authors and end-users).

  1. … 46 more files in changeset.
Improve variant matching error messages

Error messages prove to be difficult to interpret from a user point of

view. This commit tries to improve the situation by doing a couple of

things:

1. describing more clearly what the consumer is asking for. This includes,

when possible (currently only in the Java ecosystem), interpreting the

consumer attributes as a human-readable description, instead of a raw

list of attributes.

2. giving more context when possible. In particular, sometimes we fail

with an ambiguous variant error selection, but we only list the remaining

candidates, not listing the ones which were actually discarded during

selection. This proved to be particularly complex to debug from various

users (plugin authors and end-users).

  1. … 46 more files in changeset.
Improve variant matching error messages

Error messages prove to be difficult to interpret from a user point of

view. This commit tries to improve the situation by doing a couple of

things:

1. describing more clearly what the consumer is asking for. This includes,

when possible (currently only in the Java ecosystem), interpreting the

consumer attributes as a human-readable description, instead of a raw

list of attributes.

2. giving more context when possible. In particular, sometimes we fail

with an ambiguous variant error selection, but we only list the remaining

candidates, not listing the ones which were actually discarded during

selection. This proved to be particularly complex to debug from various

users (plugin authors and end-users).

  1. … 45 more files in changeset.
Improve variant matching error messages

Error messages prove to be difficult to interpret from a user point of

view. This commit tries to improve the situation by doing a couple of

things:

1. describing more clearly what the consumer is asking for. This includes,

when possible (currently only in the Java ecosystem), interpreting the

consumer attributes as a human-readable description, instead of a raw

list of attributes.

2. giving more context when possible. In particular, sometimes we fail

with an ambiguous variant error selection, but we only list the remaining

candidates, not listing the ones which were actually discarded during

selection. This proved to be particularly complex to debug from various

users (plugin authors and end-users).

  1. … 45 more files in changeset.
Improve variant matching error messages

Error messages prove to be difficult to interpret from a user point of

view. This commit tries to improve the situation by doing a couple of

things:

1. describing more clearly what the consumer is asking for. This includes,

when possible (currently only in the Java ecosystem), interpreting the

consumer attributes as a human-readable description, instead of a raw

list of attributes.

2. giving more context when possible. In particular, sometimes we fail

with an ambiguous variant error selection, but we only list the remaining

candidates, not listing the ones which were actually discarded during

selection. This proved to be particularly complex to debug from various

users (plugin authors and end-users).

  1. … 44 more files in changeset.
Use block syntax to align with kotlin example

Revert "Remove legacy play snippets"

Some of the snippets are indirectly referenced by using the `Sample`

API in AdvancedPlaySampleIntegrationTest.

This reverts commit cd94a00c6f8fe4318c86f43eaa8d05e8c8912b89.

    • -0
    • +1
    ./play/advanced/app/assets/coffeescript/console.coffee
    • -0
    • +7
    ./play/advanced/app/assets/coffeescript/squareit.coffee
    • -0
    • +9
    ./play/advanced/app/assets/javascripts/sample.js
    • -0
    • +18
    ./play/advanced/app/controllers/Application.scala
    • -0
    • +38
    ./play/advanced/app/controllers/QuestionsThreeController.scala
    • -0
    • +30
    ./play/advanced/app/controllers/hello/HelloController.java
    • -0
    • +7
    ./play/advanced/app/models/Person.scala
    • -0
    • +9
    ./play/advanced/app/views/fields.scala.html
    • -0
    • +7
    ./play/advanced/app/views/index.scala.html
    • -0
    • +16
    ./play/advanced/app/views/main.scala.html
    • -0
    • +13
    ./play/advanced/app/views/pass.scala.html
    • -0
    • +29
    ./play/advanced/app/views/person.scala.html
    • -0
    • +23
    ./play/advanced/app/views/square.scala.html
    • -0
    • +46
    ./play/advanced/build.gradle
    • -0
    • +43
    ./play/advanced/conf/application.conf
  1. … 48 more files in changeset.
Remove superfluous version

Add examples for tasks.withType method to userguide

Signed-off-by: Lars Kaulen <lars.kaulen@outlook.de>

    • -0
    • +9
    ./userguide/tasks/accessUsingType/accessUsingType.sample.conf
    • -0
    • +1
    ./userguide/tasks/accessUsingType/kotlin/settings.gradle.kts
  1. … 1 more file in changeset.
Clarify dependencies between tests and code coverage

  1. … 1 more file in changeset.
Clarify dependencies between tests and code coverage

Fixes #2921

  1. … 1 more file in changeset.
Clarify dependencies between tests and code coverage

  1. … 1 more file in changeset.
Use more recent version of JUnit Platform/Jupiter in snippets

Remove legacy play snippets

    • -9
    • +0
    ./play/advanced/app/assets/javascripts/sample.js
    • -7
    • +0
    ./play/advanced/app/models/Person.scala
    • -9
    • +0
    ./play/advanced/app/views/fields.scala.html
    • -7
    • +0
    ./play/advanced/app/views/index.scala.html
    • -16
    • +0
    ./play/advanced/app/views/main.scala.html
    • -13
    • +0
    ./play/advanced/app/views/pass.scala.html
    • -29
    • +0
    ./play/advanced/app/views/person.scala.html
    • -23
    • +0
    ./play/advanced/app/views/square.scala.html
    • -43
    • +0
    ./play/advanced/conf/application.conf
  1. … 48 more files in changeset.
Document the single lock file per project

Issue #11881

  1. … 1 more file in changeset.
Document the single lock file per project

Issue #11881

  1. … 1 more file in changeset.
Document the single lock file per project

Issue #11881

  1. … 1 more file in changeset.
Document the single lock file per project

Issue #11881

  1. … 1 more file in changeset.
Document the single lock file per project

Issue #11881

  1. … 1 more file in changeset.
Do not use org.gradle namespace in custom plugin examples

    • -4
    • +2
    ./plugins/consuming/groovy/build.gradle
  1. … 132 more files in changeset.
Do not use org.gradle namespace in custom plugin examples

    • -4
    • +2
    ./plugins/consuming/groovy/build.gradle
  1. … 87 more files in changeset.
Do not use org.gradle namespace in custom plugin examples

    • -4
    • +2
    ./plugins/consuming/groovy/build.gradle
  1. … 86 more files in changeset.
Do not use org.gradle namespace in custom plugin examples

    • -4
    • +2
    ./plugins/consuming/groovy/build.gradle
  1. … 166 more files in changeset.
Do not use org.gradle namespace in custom plugin examples

    • -4
    • +2
    ./plugins/consuming/groovy/build.gradle
  1. … 166 more files in changeset.
Use a property for LockMode

This is more inline with modern Gradle APIs and enables the usage of

finalized value instead of doing it internally.

  1. … 8 more files in changeset.