Ability to force an evaluation when configure on demand = true


(Mark E. Scott, Jr.) #1

Continuing the discussion from Can't call evaluate() on Project instances returned from ProjectBuilder with gradle-1.12-rc-1:

I would kill right now for the ability to force evaluation of projects. In one of our large Gradle solutions, with 150+ projects, I have one particular project that requires all other projects be evaluated (to be able to use plugins.hasPlugin(‘java’)). However, this project/task is rarely ever run by a developer, and shouldn’t force evaluation of all projects unless it’s scheduled to run.


(Mark Vieira) #2

You can force evaluation of one project from another by establishing a dependency. For example, you can place the following in your build script:

evaluationDependsOn ':someOtherProject'