Gradle

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Publish 5.6.2-20190916230041+0000

Fix test not to expect scripts to implement either `Project` or `Settings`

Make DefaultResourceHandler.Factory an interface we can stub out in workers

Merge pull request #10734 from gradle/gh/task-resources/hide-public

Hide task shared resources from the public api for now

Remove reference to Gradle UI

Introduce a ProjectDirectoryProvider to allow worker executor to find the project directory

Accept Kotlin DSL init script API changes

Remove `Settings` interface from Kotlin DSL settings script type hierarchy

Change tests not to expect Kotlin scripts to implement `Gradle`, `Settings` or `Project`

Fix the decoration on FileSystemOperations and ExecOperations closures

Remove `Gradle` interface from Kotlin DSL init script type hierarchy

`PluginAware` will be removed from all script type hierarchies in a

future commit.

Use ISO 8601 log format for logged daemon messages

Use ISO 8601 log format for logged daemon messages

Mention contributor in release notes

    • -1
    • +2
    /subprojects/docs/src/docs/release/notes.md
Pass the mutating Set directly instead of a plain boolean

Split complex test into multiple tests

Clarify method's purpose with clearer name

Fix sample test failure

Merge pull request #10543 from vlsi/sign_hash

signing plugin: use SHA512 instead of SHA1 when signing artifacts

Rework warning around additional artifacts

Rework warning around additional artifacts

Rework warning around additional artifacts

Add reified extensions for ComponentMetadataHandler

Add reified extensions for ComponentMetadataHandler

Add reified extensions for ComponentMetadataHandler

Merge pull request #10731 from gradle/marc/junit-platform-vintage-fixes

Fix executing Specs tests via JUnit Platform and Vintage engine and remove unnecessary workarounds

Fix application of dependency rules in realized metadata version

The rules for dependencies and dependency constraints were not applied

if the variant itself was added by a rule.

This commit also no longer attempts to apply any rule to the realized

version of 'pure maven configurations'. For Maven, we always use the

derived variants and always use variant matching. Therefore, rules are

never applied to the legacy configurations, but only to the derived

variants.

Follow up to #10368

Change exception to InvalidUserCodeException

Issue #10532

Change exception to InvalidUserCodeException

Issue #10532

Change exception to InvalidUserCodeException

Issue #10532