Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Always instrument build logic, regardless of whether the configuration cache is enabled or not.

This change means that the same class paths and `ClassLoader` hierarchy are used regardless of whether or not the configuration cache is enabled. It also means that some cross-cutting instrumentation can later be added.

  1. … 6 more files in changeset.
Create new configuration caching compatible enterprise plugin contact point (#13372)

  1. … 122 more files in changeset.
Make api non null

The content filter action is always non null, using Actions.doNothing()

where needed instead.

Issue #13038

    • -0
    • +20
    ./java/org/gradle/plugin/use/internal/package-info.java
  1. … 6 more files in changeset.
Handle content filter for plugins repositories

Given that settings defined repositories are added to project

buildscript repositories, they need to handle content filtering

independently for each project.

This commit fixes that by letting the plugin repository wrapper handle

the content filtering aspect, allowing a different set of filtering for

each project.

Fixes #13038

  1. … 7 more files in changeset.
Temporarily disable instrumentation of build logic added via the build script classpath when configuration caching is not enabled.

Other build logic is still instrumented.

  1. … 11 more files in changeset.
Revert "Apply undeclared system property instrumentation to plugins injected through TestKit."

This reverts commit 4a2a0e7faa6eb540fb58f4b55e8cd019073442c9.

  1. … 9 more files in changeset.
Apply undeclared system property instrumentation to plugins injected through TestKit.

  1. … 9 more files in changeset.
Apply undeclared system property instrumentation to plugins injected through TestKit.

  1. … 9 more files in changeset.
Apply system property read detection to Groovy DSL scripts.

  1. … 36 more files in changeset.
Allow client of `CachedClasspathTransformer` to specify what purpose the result will be used for, so that different transformations can be applied.

In this commit, the parameter has no effect.

  1. … 14 more files in changeset.
Remove some unused methods and fields.

  1. … 4 more files in changeset.
Revert "Auto apply PreCompiledScriptPluginsPlugin"

This reverts commit 4c3b8e4ff86a8f4dce1d375f1fc8835e1bf31498.

# Conflicts:

# subprojects/plugin-development/src/integTest/groovy/org/gradle/plugin/devel/plugins/PreCompiledScriptPluginsPluginIntegrationTest.groovy

  1. … 2 more files in changeset.
Auto apply PreCompiledScriptPluginsPlugin

In order to discover, precompile and wire-up Groovy plugins.

  1. … 2 more files in changeset.
Minor refactorings

Add plugin repository before transforming plugin requests as those might materalize the descriptor already

  1. … 1 more file in changeset.
Make the various execution services available in build scope, using the build's root directory as the base directory for file resolution.

  1. … 8 more files in changeset.
make inner classes static where possible

Signed-off-by: Steven Crockett <crockett.j.steven@gmail.com>

  1. … 42 more files in changeset.
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.
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.
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

  1. … 6 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.
Replace `FileResolver.resolveFilesAsTree()` and `compositeFileTree()` with `FileCollectionFactory`.

  1. … 44 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.
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.
Add missing @Override to all modules

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

  1. … 990 more files in changeset.
Simplify mechanism to auto apply the build scan plugin when running with instant execution, and remove dependency from `instant-execution` to `plugin-use` project.

  1. … 9 more files in changeset.
Add some basic support for generating a build scan when running with instant execution enabled.

  1. … 9 more files in changeset.