Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output.
I know its a misconfiguration in the gretty plugin. There are other plugins that have similar misconfiguration.
So i guess gretty should fix it or plugin makers.
Is there a way to say to plugins that they should ignore some dependencies? Or should i tell gradle lint, and i also have the same issue with pitest (i think). Should i tell them to, or can i configure it to ignore gretty. It seems a bit of a pity that one plugin can break other plugins.
When there is a reference to a jar that is not in a repo, other plugins start failing. (I guess only plugins that need to know this specific information start failing).
I know it sounds a bit stupid to use a plugin that is broken, but the functionality that we use the plugin for works fine.