You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
👍
Silently ignoring non-existing init scripts did bite me quite some times and I think it is surprising that we do no fail the build if the init script is not found.
If any of the init scripts specified on the command line does not exist
or is not a file, the build will fail.
Issue: #4672
Signed-off-by: Patrik Erdes <patrik@erdes.se>
When explicitly including an init script (via
-I
or--init-script
), Gradle will silently ignore the init script if it does not exist.Expected Behavior
gradle -I doesNotExist.gradle ...
would fail.Current Behavior
gradle -I doesNotExist.gradle ...
succeeds as if the init script was not requested.Context
If someone uses init scripts to inject additional configuration conditionally (e.g., on CI only), simple file renames can silently break things.
We had this happen on the gradle/gradle build when we converted our init script to Kotlin.
The text was updated successfully, but these errors were encountered: