[GRADLE-3534] Applying the eclipse or idea plugin breaks configure on demand Created: 24/Aug/16  Updated: 24/Aug/16  Resolved: 24/Aug/16

Status: Resolved
Project: Gradle
Affects Version/s: 3.0
Fix Version/s: 3.1-rc-1

Type: Bug
Reporter: Benjamin Muschko Assignee: Stefan Wolf
Resolution: Fixed Votes: 0


When the idea or eclipse plugins are applied in an allprojects Closure then the evaluation of all projects is forced even if configureOnDemand is requested.

include 'a', 'b'
allprojects {
    apply plugin: 'idea'
subprojects {
    apply plugin: 'java'

When running :a:build with --configure-on-demand the project b is evaluated, too.

Build scans for another example project:
2.14.1: https://scans.gradle.com/s/r2l6bdfgcq5om
3.0: https://scans.gradle.com/s/k6jvlsxn2ssz2

In 3.0, all projects are configured. In 2.14.1, only project1 is configured.

Suspect that it's the idea (and eclipse?) plugin that's causing it. Setting a breakpoint BuildScriptProcessor.execute() shows the Idea plugins doing something with the projects we don't want to be configured.

Generated at Wed Jun 30 12:51:19 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.