userguide

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Autodetect TestFramework if none is configure explicitly

When the TestFramework of a Test task is not configured explicitly it

used to default to `useJUnit()`. Now, the task's classpath is inspected

for a junit-platform-engine.jar or testng.jar. If one of them is found,

the task uses the JUnit Platform or TestNG to execute tests,

respectively.

Since we have internal dependencies on the JUnit Platform and TestNG,

all Test tasks in our own build are configured to `useJUnit()` and

explicitly.

  1. … 11 more files in changeset.
Remove task replacement sample from userguide

    • -7
    • +0
    ./tutorial/replaceTask/groovy/build.gradle
    • -1
    • +0
    ./tutorial/replaceTask/kotlin/settings.gradle.kts
    • -1
    • +0
    ./tutorial/replaceTask/replaceTask.out
  1. … 1 more file in changeset.
Remove old and unused feature preview flags

This removes the preview flags completely that have already bean

deactivated for several Gradle versions and caused a deprecation

warning that they are being removed in Gradle 6.0.

  1. … 1 more file in changeset.
Remove old and unused feature preview flags

This removes the preview flags completely that have already bean

deactivated for several Gradle versions and caused a deprecation

warning that they are being removed in Gradle 6.0.

  1. … 1 more file in changeset.
Adjust tests and samples to new metadata sources defaults

    • -2
    • +0
    ./java/fixtures/groovy/settings.gradle
    • -2
    • +0
    ./java/fixtures/kotlin/settings.gradle.kts
  1. … 84 more files in changeset.
Remove enableFeaturePreview('GRADLE_METADATA') from samples

    • -2
    • +0
    ./java/fixtures/groovy/settings.gradle
    • -2
    • +0
    ./java/fixtures/kotlin/settings.gradle.kts
  1. … 4 more files in changeset.
Remove enableFeaturePreview('GRADLE_METADATA') from samples

    • -2
    • +0
    ./java/fixtures/groovy/settings.gradle
    • -2
    • +0
    ./java/fixtures/kotlin/settings.gradle.kts
  1. … 4 more files in changeset.
Remove enableFeaturePreview('GRADLE_METADATA') from samples

    • -2
    • +0
    ./java/fixtures/groovy/settings.gradle
    • -2
    • +0
    ./java/fixtures/kotlin/settings.gradle.kts
  1. … 4 more files in changeset.
Adjust tests and samples to new metadata sources defaults

  1. … 12 more files in changeset.
Adjust tests and samples to new metadata sources defaults

  1. … 12 more files in changeset.
Adjust tests and samples to new metadata sources defaults

  1. … 12 more files in changeset.
Sweep up a few more references to announce plugin

  1. … 3 more files in changeset.
Add documentation for subgraph version constraints

  1. … 4 more files in changeset.
Remove osgi plugin

    • -23
    • +0
    ./tutorial/osgi/groovy/build.gradle
    • -1
    • +0
    ./tutorial/osgi/groovy/settings.gradle
    • -26
    • +0
    ./tutorial/osgi/kotlin/build.gradle.kts
    • -1
    • +0
    ./tutorial/osgi/kotlin/settings.gradle.kts
  1. … 37 more files in changeset.
Remove osgi plugin

    • -23
    • +0
    ./tutorial/osgi/groovy/build.gradle
    • -1
    • +0
    ./tutorial/osgi/groovy/settings.gradle
    • -26
    • +0
    ./tutorial/osgi/kotlin/build.gradle.kts
    • -1
    • +0
    ./tutorial/osgi/kotlin/settings.gradle.kts
  1. … 37 more files in changeset.
Add documentation about Gradle Module Metadata

This mentions Gradle Module Metadata works with other

file formats, how to avoid its publication and how what

happens when you publish a component that uses Gradle

specific features.

  1. … 1 more file in changeset.
Add documentation about Gradle Module Metadata

This mentions Gradle Module Metadata works with other

file formats, how to avoid its publication and how what

happens when you publish a component that uses Gradle

specific features.

  1. … 1 more file in changeset.
Reorganize the "publishing" section

Integrate it into the dependency management docs.

This commit also adds documentation about custom component publication.

  1. … 11 more files in changeset.
Reorganize the "publishing" section

Integrate it into the dependency management docs.

This commit also adds documentation about custom component publication.

  1. … 11 more files in changeset.
Improve rendering of artifacts in outgoing variants report

This commit changes how artifacts are rendered, so that if they

are associated with a type (either explicit or derived), we show

the corresponding `artifactType` attribute.

This helps understanding a bit what can happen in an Android build

where multiple variants may have the same attributes, but only

differ on the artifact type derived from the artifacts carried

by the variant.

  1. … 2 more files in changeset.
Improve rendering of artifacts in outgoing variants report

This commit changes how artifacts are rendered, so that if they

are associated with a type (either explicit or derived), we show

the corresponding `artifactType` attribute.

This helps understanding a bit what can happen in an Android build

where multiple variants may have the same attributes, but only

differ on the artifact type derived from the artifacts carried

by the variant.

  1. … 2 more files in changeset.
Add advanced example of producing a new variant

This example shows how to produce a new variant of a library that

can be used in a specific context from the consumer side. This

involves reusing existing attributes as well as defining compatibility

rules.

  1. … 8 more files in changeset.
Add advanced example of producing a new variant

This example shows how to produce a new variant of a library that

can be used in a specific context from the consumer side. This

involves reusing existing attributes as well as defining compatibility

rules.

  1. … 10 more files in changeset.
Add advanced example of producing a new variant

This example shows how to produce a new variant of a library that

can be used in a specific context from the consumer side. This

involves reusing existing attributes as well as defining compatibility

rules.

  1. … 10 more files in changeset.
Add advanced example of producing a new variant

This example shows how to produce a new variant of a library that

can be used in a specific context from the consumer side. This

involves reusing existing attributes as well as defining compatibility

rules.

  1. … 8 more files in changeset.
Add advanced example of producing a new variant

This example shows how to produce a new variant of a library that

can be used in a specific context from the consumer side. This

involves reusing existing attributes as well as defining compatibility

rules.

  1. … 9 more files in changeset.
Add advanced example of producing a new variant

This example shows how to produce a new variant of a library that

can be used in a specific context from the consumer side. This

involves reusing existing attributes as well as defining compatibility

rules.

  1. … 10 more files in changeset.
Add advanced example of producing a new variant

This example shows how to produce a new variant of a library that

can be used in a specific context from the consumer side. This

involves reusing existing attributes as well as defining compatibility

rules.

  1. … 8 more files in changeset.
Add section about cross-project publications

This commit introduces documentation explaining _one_ way to

perform safe, cross-project boundaries by exposing configurations

which are either consumable or resolvable.

It does _not_ explain the variant-aware version of this which

requires more ceremony.

  1. … 1 more file in changeset.
Add section about cross-project publications

This commit introduces documentation explaining _one_ way to

perform safe, cross-project boundaries by exposing configurations

which are either consumable or resolvable.

It does _not_ explain the variant-aware version of this which

requires more ceremony.

  1. … 1 more file in changeset.