Gradle

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Ensure that task is created with mutable project lock

Make ivy-publish, maven-publish, and java-library distribution plugins lazy

...mostly. The publish plugins still eagerly realize tasks if the publications are needed

Remove dist plugin from list of misbehaving plugins

Signed-off-by: Kevin Macksamie <kevin.macksamie@gmail.com>

Reuse the build script generation infrastructure to generate more of the Gradle build scripts when converting a Maven build.

Merge pull request #6430 from gradle/wolfs/samples-as-input-to-integTest

Add samples as an input to `integTest:integTest`

Include Kotlin DSL samples in the plugins doc chapter

See #6424

    • -116
    • +105
    /subprojects/docs/src/docs/userguide/plugins.adoc
  1. … 97 more files in changeset.
Merge pull request #6406 from gradle/eskatos/docs-kts/authoring-maintainable-build-scripts

Add Kotlin DSL samples to Authoring maintainable build scripts user manual chapter

Reuse the build script generation infrastructure to generate more of the Gradle build scripts when converting a Maven build.

Disallow more project configuration hooks from lazy configuration actions

Replace logging of configuration name with identity path

Previously dependency locking was only reporting the name of the

configuration. This however made it hard to pinpoint a source of problem

in a multi project build. With this change, now the full identity path

of the configuration is reported.

Fixes #6384

docs/authoring_maintainable_build_scripts tests requires Java 8

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

Add samples as an input to `integTest:integTest`

Given that the user guide samples will be tested there.

    • -0
    • +1
    /subprojects/integ-test/integ-test.gradle
Merge pull request #6408 from gradle/wolfs/deprecations/strict-input-validation

Forbid registering invalid file inputs via the runtime API

    • -0
    • +1
    /subprojects/docs/src/docs/release/notes.md
docs/build-scripts-basics fix samples integration tests

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

docs/authoring_maintainable_build_scripts fix samples integration tests

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

Rebaseline performance test

Test failed on master after seemingly unrelated changes. Putting a new

baseline to have time to investigate properly.

Change the `init` task to reuse the build script generation infrastructure to generate part of the root build script when generating a Gradle build from a Maven build.

Move some classes around in "build-init" to break package cycle.

Change the `init` task to reuse the build script generator infrastructure to generate the Gradle settings file for a Maven build, rather than creating a string with ad hoc formatting.

Minor tweak to layout of prompt used to ask user to select an option from a list.

Change `init` task so that it uses a default source package name that is derived from the project name, rather than an empty package name.

Use null-safe operator to fix flaky test #1425

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

This is an attempt to fix #1425. We simply apply Groovy's null-safe operator to see if it works.

Revert "Fix customLogger Kotlin DSL sample and enable test"

This reverts commit 4fc760927bbf23848309ab310e02c07789e823d7.

Change the `init` task to generate a simple `.gitignore` file in the build's root directory.

Refactor the build init infrastructure to distinguish between initializers that generate a Gradle build from some existing build and those that generate a new build an supporting files from scratch.

Mark test as leaking files.

Improve the `init` task when in interactive mode when a Maven build is present in the current directory, by first asking the user if they would like to generate a Gradle build for the Maven build. If the user answers 'yes', proceed without asking any further questions. If the user answers 'no', only then ask the user to select which type of build they would like to create.

  1. … 5 more files in changeset.
Allow the user to be prompted with a yes/no question that has a default response.

Merge branch 'release' into 'master'

Change the `init` task to default to Kotlin DSL when generating Kotlin builds.