Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Setting non-existent Kotlin build script in settings.gradle should not fail #302
Setting non-existent build script file with
results in build failing with:
It should not fail as build scripts are optional.
I think there are two different use cases here:
That reasoning tells me we shouldn't be fixing 1 at the scripting provider level but at a higher-level.
The Gradle runtime already distinguishes the various use cases and fails with a proper error message when it has to.
A scripting provider may decide to add stuff to build scripts, e.g. base plugins like we envision in order to solve #320. Even when the file isn't there because it is optional.
So, I think this boils down to the contracts of
When it comes to the settings scripts there actually are three cases:
In the 1st case the
In the 2nd case it is a
In the 3rd case the