Since Gradle 5.1 a new API exists to register and configure tasks lazily to avoid creating tasks during configuration phase.
https://docs.gradle.org/current/userguide/task_configuration_avoidance.html
Currently the Ebean Plugin iterates through a bunch of compile tasks by name and while doing so forces Gradle to create these tasks during configuration time instead of execution time.
One can easily see this when running ./gradlew help --scan on any project using the Ebean plugin. On the performance section Gradle shows which tasks have been created during which Gradle phase. Executing the help task should not cause any other tasks to be created.
Since Gradle 5.1 a new API exists to register and configure tasks lazily to avoid creating tasks during configuration phase.
https://docs.gradle.org/current/userguide/task_configuration_avoidance.html
Currently the Ebean Plugin iterates through a bunch of compile tasks by name and while doing so forces Gradle to create these tasks during configuration time instead of execution time.
One can easily see this when running
./gradlew help --scanon any project using the Ebean plugin. On the performance section Gradle shows which tasks have been created during which Gradle phase. Executing the help task should not cause any other tasks to be created.