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

  1. … 3 more files in changeset.
Integrate with Gradle Enterprise plugin 3.0 (#11041)

  1. … 50 more files in changeset.
Fail better when using --scan and an old incompatible scan plugin

  1. … 3 more files in changeset.
Update scan support for Gradle Enterprise plugin 3.0

Gradle 6 is now only compatible with this plugin.

  1. … 34 more files in changeset.
Make paths/names of included builds immutable (#10998)

Changes the “build path” for included builds to be determined at inclusion time based on the directory name, or a user supplied override. Previously, we tried to use the root project name defined in the included build. This caused a lot of complexity due to it not being known until part way through building the included build.

This change also disallows use of `buildSrc` as a project name, as it collides with the `buildSrc` nested build.

  1. … 72 more files in changeset.
Make paths/names of included builds immutable

  1. … 32 more files in changeset.
Add a `add-plugin` CLI option

This commit introduces a new CLI flag, `--add-plugin`, which allows adding a plugin to a build

directly from the command line. The main advantage of this is that there's no need to have a

build file to be able to download an apply a plugin.

There are different use cases for this, but mainly, this is about _bootstraping_ plugins.

For example, the vert.x team could publish a plugin which generates a templated Gradle build.

All the user would have to do would be something like:

`gradle --add-plugin com.vertx.bootstrap:1.5`

and then the plugin would take care of generating a build.

Another use case is to add diagnostics (build scans is an example of this but there's already

a built-in mechanism, --scan, to do this).

This spike is _compatible with included builds_, meaning that you can bootstrap with

a plugin currently in development using `--include-build`.

  1. … 3 more files in changeset.
Use notFound() in composite build plugin resolver

  1. … 5 more files in changeset.
Remove "self-resolving" plugin resolver since injected plugins now come from included builds

    • -2
    • +2
    ./plugin/internal/PluginUsePluginServiceRegistry.java
  1. … 6 more files in changeset.
Revert "Disable auto apply for scan plugin (temporally) (#10783)"

This reverts commit 5b1d0543e4b76fc51aafb5d2fc757dcf086b0e4c.

  1. … 5 more files in changeset.
Disable auto apply for scan plugin (temporally) (#10783)

* Disable auto apply for scan plugin

This will be reenabled as soon as possible once we integrated that gradle snapshot into the ge

  1. … 5 more files in changeset.
Fix checkstyle and ignore correct test

  1. … 3 more files in changeset.
Disable auto apply for scan plugin

Fixes for previous commit.

    • -5
    • +8
    ./plugin/internal/PluginUsePluginServiceRegistry.java
  1. … 6 more files in changeset.
Replace `FileResolver.resolveFilesAsTree()` and `compositeFileTree()` with `FileCollectionFactory`.

    • -5
    • +8
    ./plugin/internal/PluginUsePluginServiceRegistry.java
  1. … 44 more files in changeset.
Replace `FileResolver.resolveFilesAsTree()` and `compositeFileTree()` with `FileCollectionFactory`.

    • -5
    • +8
    ./plugin/internal/PluginUsePluginServiceRegistry.java
  1. … 44 more files in changeset.
Apply `Inner class may be 'static'` inspection the whole project

  1. … 41 more files in changeset.
Apply `Anonymous type can be replaced with lambda` inspection the whole project

    • -7
    • +4
    ./plugin/internal/PluginUsePluginServiceRegistry.java
  1. … 662 more files in changeset.
Apply `Explicit type can be replaced with <>` inspection the whole project

  1. … 905 more files in changeset.
Verify error messages in integration test

  1. … 1 more file in changeset.
Add better validation for `plugins` block in `pluginManagement`

  1. … 1 more file in changeset.
Add better validation for `plugins` block in `pluginManagement`

  1. … 1 more file in changeset.
Allow plugin versions to be specified in Settings

This is a hack/spike implementation.

  1. … 2 more files in changeset.
Allow plugin versions to be specified in Settings

This is a hack/spike implementation.

  1. … 2 more files in changeset.
Allow plugin versions to be specified in `pluginManagement`

This change provides a mechanism for centralized management of plugins

applied within a multi-project build. When a plugin version is registered

in the settings script, build scripts are able to apply the plugin using

the `plugins` block without specifying a version.

  1. … 4 more files in changeset.
Allow plugin versions to be specified in `pluginManagement`

This change provides a mechanism for centralized management of plugins

applied within a multi-project build. When a plugin version is registered

in the settings script, build scripts are able to apply the plugin using

the `plugins` block without specifying a version.

  1. … 4 more files in changeset.
Imports

  1. … 17 more files in changeset.
Imports

  1. … 17 more files in changeset.
Extract anonymous classes to static inner classes

  1. … 145 more files in changeset.
Extract anonymous classes to static inner classes

  1. … 146 more files in changeset.