Yes, I’m sure. A separate test project does appear to work as expected (showing compile errors w/o needing --debug or disabling forking). Not sure why there’s a difference because my build files are similar (just fewer dependencies in one and it’s not part of a multi-project build). I keep having issues with the stock AST transformations (which is the problem I alluded to earlier; when forking is disabled groovyc fails to recognize them and compilation fails). The other project doesn’t use them.
For the affected project when I specify the --debug flag the output goes from Ivy resolving dependencies to the TaskExecutionException. The exception lists the forked groovyc exit code as the only cause, but when I disable forking the chain of exceptions changes to a TEE caused by ‘Compilation Failed’ with MultipleCompilationErrorsException as the root cause. The root exception’s message includes the compile error output from groovyc.
I’ll see if I can sanitize the project enough to provide it as a test case for you.