This message was deleted.

It is, and it is also just logical if you think about the purpose. In the

pluginManagement

block you can influence plugin resolution like defining plugin repositories, default plugin versions, included plugin builds, ... All these can influence the settings plugins that are applied to the settings script and are available in its classpath, so it has to be evaluated up-front, or you cannot even compile the settings script when using a class from such a plugin. Similar for the

buildscript

block, you there can define dependencies that are used within the buildscript and are part of its compile classpath, so it must be evaluated up-front, or the build script could maybe not even compile. From a cursory look it might indeed be missing in the docs. The only reference I found quickly is in the upgrade notes: https://docs.gradle.org/current/userguide/upgrading_version_5.html#the_pluginmanagement_block_in_settings_scripts_is_now_isolated There actually also

buildscript

and

plugins

blocks are mentioned. You might want to open a feature request or pull request to clarify that better in the docs. 🙂

Big thanks @Vampire! This was mega useful information and I’ll definitely try to at least open a feature request 👍