Gradle

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Fix handling of “no settings” case WRT auto applied plugins and classpath

Some invocation args (e.g. -b) cause us to create two settings objects,

with the subsequent being empty.

Previously we were applying the auto

apply plugins to both, and inheriting the empty's classpath into the

rest of the build.

Now, we don't auto apply any plugins to the empty and have it inherit

the real settings script's classpath (which also makes it available to

the rest of the build tree).

Closes #11101

Restore `build-scan` plugin syntax in Kotlin scripts

Closes #11095

Recognize contributor

    • -0
    • +1
    /subprojects/docs/src/docs/release/notes.md
Remove duplicated test, this is covered by MapPropertyIntegrationTest

Merge pull request #11118 from gradle/jjohannes/platform-disambiguation

Allow regular and enforced variants of one platform to be selected together. Also, always disambiguate between them if one has to be selected.

Cleanup code in PlatformSupport

Increase cache layout version

Rename: `-enforced-platform` -> `-derived-enforced-platform`

Remove `platform` dsl from constraint handler

These shortcuts define details of a dependency like attributes,

requested capabilities and 'endorse strict' status. These things

can not be defined on constraints. So these methods only cause

inconsistent behavior.

One can use constraints in combination with platforms like this to

control platform versions:

dependencies {

api platform("org:platform")

constraints {

api "org:platform:1.0"

}

}

    • -3
    • +0
    /subprojects/docs/src/docs/dsl/org.gradle.api.artifacts.dsl.DependencyConstraintHandler.xml
Use a different 'shadow capability' for enforced platform

This allows both 'regular' and 'enforced' platform of the same

component to be selected. In order to make this work, support

for projects having shadow capability needed to be added.

Always apply all Category disambiguation rules

Before, parts of the platform disambiguation were only done when

using the 'java-platform' plugin. However, other consumers

may also require all rules (see #11091)

Add tests to reproduce platform disambiguation issues in Gradle 6 RC1

See: https://github.com/gradle/gradle/issues/11091

Fix spelling: it's coordinates -> its coordinates

Fix publication warning report

An output is no longer presented if all warnings are silenced by variant

name.

Fixes #11111

Introduce new metadata marker for Gradle 6 (#11109)

See: https://github.com/gradle/gradle/issues/11105

Refactored to correctly handle 'null' from remapper

Issue #11027

Signed-off-by: lingocoder <coder@lingocoder.com>

Add back @Incubating for enforced platform API

These were removed in https://github.com/gradle/gradle/pull/10040

but the features is likely to be adjusted in 6.x

Fix typo in release notes

    • -1
    • +1
    /subprojects/docs/src/docs/release/notes.md
Fix link in capabilities conflict handling section in documentation

Correct handling of multiple svc provider impls in a single SPI file

Issue: #11027

Signed-off-by: lingocoder <coder@lingocoder.com>

Fix Smoke Tests that fail on Java 13

Signed-off-by: Paul Merlin <paul@gradle.com>

Fix deprecation message for Checkstyle methods

Rename „META-INF/services“ to „META-INF/groovy“

Issue: #11028

Signed-off-by: lingocoder <coder@lingocoder.com>

Update to 6.0RC1

    • -1
    • +1
    /gradle/wrapper/gradle-wrapper.properties
Fix TAPI tests

Make Zinc version constant public

And use it in Javadoc

Inline Android relocation test (#11070)

Inline Android relocation test

Correct illegal cmd lines to exec modules' main class

Issue: #10825

Signed-off-by: lingocoder <coder@lingocoder.com>

Pin santaTracker to older version

to see if the performance tests are fixed.

    • -1
    • +1
    /subprojects/performance/templates.gradle
Update docs to say Scala 2.13 can be compiled