Gradle

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Add some test coverage

Add some test coverage

Add some test coverage

Fix navigation to publishing chapter

Publishing remains a top level chapter. While it shares a lot with

dependency management, it is a specific topic that can be viewed in

isolation.

* Removed entry from dependency management section

* Corrected link in top level

Fix navigation to publishing chapter

Publishing remains a top level chapter. While it shares a lot with

dependency management, it is a specific topic that can be viewed in

isolation.

* Removed entry from dependency management section

* Corrected link in top level

Fix navigation to publishing chapter

Publishing remains a top level chapter. While it shares a lot with

dependency management, it is a specific topic that can be viewed in

isolation.

* Removed entry from dependency management section

* Corrected link in top level

Fix navigation to publishing chapter

Publishing remains a top level chapter. While it shares a lot with

dependency management, it is a specific topic that can be viewed in

isolation.

* Removed entry from dependency management section

* Corrected link in top level

Allow ValidateStep to report validation warnings

Deprecated `force` on first-level dependencies

This commit deprecates using `force` in favor of using the

new "strictly" behavior. The "force" flag is still used

internally, in particular in case of virtual platforms, but

its usage should be discouraged as we have a solution which

is better now.

  1. … 9 more files in changeset.
Deprecated `force` on first-level dependencies

This commit deprecates using `force` in favor of using the

new "strictly" behavior. The "force" flag is still used

internally, in particular in case of virtual platforms, but

its usage should be discouraged as we have a solution which

is better now.

  1. … 4 more files in changeset.
Deprecated `force` on first-level dependencies

This commit deprecates using `force` in favor of using the

new "strictly" behavior. The "force" flag is still used

internally, in particular in case of virtual platforms, but

its usage should be discouraged as we have a solution which

is better now.

  1. … 9 more files in changeset.
Update auto apply scan plugin to 2.4.2 (#10535)

Emit validation warning in execution engine

Break something for testing...

Broken link check as part of sanity check and archive report on CI

Broken link check as part of sanity check and archive report on CI

Rename TaskValidationException to WorkValidationException

And move it to :model-core.

Rename ParameterValidationContext to WorkValidationContext

  1. … 27 more files in changeset.
Fix broken link

Remove extra new-line

Do not split tests on AllVersionsCrossVersion (#10702)

See https://github.com/gradle/gradle-private/issues/2693

This commit disable test splits for AllVersionsCrossVersion.

    • -2
    • +2
    /.teamcity/Gradle_Check/model/CIBuildModel.kt
Do not split tests on AllVersionsCrossVersion (#10702)

See https://github.com/gradle/gradle-private/issues/2693

This commit disable test splits for AllVersionsCrossVersion.

    • -2
    • +2
    /.teamcity/Gradle_Check/model/CIBuildModel.kt
Add more information about potentially breaking changes in Gradle 6

Merge pull request #10696 from gradle/wolfs/remove-getInstantiatorForNext-usage

Remove leftover reference to `getInstantiatorForNext`

Add todos for remaining tasks

Add todos for remaining tasks

Add todos for remaining tasks

Add todos for remaining tasks

Use "real" cache layout version

Merge pull request #10607 from gradle/jjohannes/maven-artifacts-and-packaging

Do not change extension of published artifact based on pom packaging