[GROOVY-9491] Groovy still runs despite grapeConfig.xml is malformed

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 2.5.10, 3.0.2
• Component/s: groovy-runtime
• Assignee: Unassigned
• Reporter: Arseniy Tashoyan
• Created: 29/Mar/20 19:57
• Updated: 29/Mar/20 20:00

Description

With a malformed grapeConfig.xml, groovy prints a warning on standard error, then continues to run with some built-in default Grape configuration:

Local Ivy config file '/Users/user/workspace/custom/src/main/resources/grapeConfig.xml' appears corrupt - ignoring it and using default config instead
...

This leads to unpredictable behavior - for example, a wrong version of library in the classpath downloaded from a wrong location. Such issue is quite hard to troubleshoot, because the actual failure occurs at arbitrary point of time and gives no clue about the root cause.
Instead, groovy should fail with non-zero code.
The warning on stderr might be visible when running a script in a console. But for a CI system, where no human reads stderr unless a build or test failed, this warning is almost invisible.