Clone Tools
  • last updated a few seconds ago
Constraints: committers
Constraints: files
Constraints: dates
Temporarily reverting everything since 810f052813ea0835dc7e9d3eb87bca005815db64 for 3.0-milestone-1 release

  1. … 199 more files in changeset.
Add `apply false` option to `plugins` block

This solves two use cases at once:

- only using some classes from a plugin without applying it

- applying a plugin to sub-projects without applying it to the root project

  1. … 18 more files in changeset.
Revert plugins.subprojects syntax, as we are considering another solution

  1. … 37 more files in changeset.
Allow applying plugins to subprojects using new DSL

This change adds new `subprojects` and `allprojects` methods to the `plugins`

DSL, which allow users to apply plugins to multiple subprojects at once.

The plugins are resolved in the context of the parent project and put on

the parent's classpath. This ensures that the parent can cross-configure its

children. A side-effect is that unrelated subprojects will see those plugin

classes too, even though they are not applied to them.

The `plugins` block is no longer backed by an AST transformation, but is

now compiled, exactly like the `buildscript` and `pluginRepositories` blocks.

This will give users greater flexibility to conditionally apply plugins in the

future. Currently no access is granted to any methods outside of the `plugins`

API though.

  1. … 38 more files in changeset.
Renamed PotentialPluginWithId to PluginImplementation.

  1. … 13 more files in changeset.
Changed PluginRegistry.lookup() to accept a PluginId. Added some test coverage and simplified implementation of DefaultPluginRegistry.

  1. … 8 more files in changeset.
Changed plugin resolution so that the PotentialPlugin located during resolution is not discarded during application.

  1. … 8 more files in changeset.
Changed PluginResolutionResult so that a PluginResolution is used for both legacy and non-legacy plugins. Moved the distinction between these to PluginResolveContext.

  1. … 7 more files in changeset.
Remove AppliedPlugins and make PluginManager the public replacement for PluginContainer.

+review REVIEW-5298

  1. … 97 more files in changeset.
Fixes for plugin {} type resolution after recent changes to PluginManager.

+review REVIEW-5214

  1. … 4 more files in changeset.
Make withId(), hasPlugin() etc. work for qualified and unqualified “privileged” names regardless of how the plugin was applied.

+review REVIEW-5214

  1. … 13 more files in changeset.
Centralise detection/handling of different types of plugins.

+review REVIEW-5214

  1. … 63 more files in changeset.
Add ability to apply rule source only plugins via plugins {} block

+review REVIEW-5214

  1. … 20 more files in changeset.
Add support for applying rule sources that don't implement Plugin using id via PluginAware.apply()

+review REVIEW-5214

  1. … 34 more files in changeset.
Allow core plugins to be used via name and qualified id consistently.

+review REVIEW-5154

  1. … 150 more files in changeset.
Rework the PluginResolver API to support more complex outcomes.

  1. … 9 more files in changeset.
Apply new style plugins on top of the core impl classloader and expose nothing to the plugin target.

  1. … 12 more files in changeset.
REVIEW-4921 - add PluginId type.

Also addresses REVIEW-4918.

  1. … 15 more files in changeset.
REVIEW-4926 - unit test for core plugin resolver

    • -0
    • +91