[GRADLE-3534] Applying the eclipse or idea plugin breaks configure on demand Created: 24/Aug/16 Updated: 24/Aug/16 Resolved: 24/Aug/16
|Reporter:||Benjamin Muschko||Assignee:||Stefan Wolf|
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.
When running :a:build with --configure-on-demand the project b is evaluated, too.
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.