How to make gradle stop getting a not existing jar from a third party maven repo

You say you added this snippet.
So if you did not define that repository before at all, it is probably defined by one of the plugins you apply - which is bad practice too for public plugins.
If that is the case, you just add another repository with the same URL later, but the original repository is still queried first.
You might be able to clear() the repositories first and then add your desired ones.
Or you could instead use the “exclusive content” setup further down in the docs I linked to not say “this repo does not have X” but instead “X should only be taken from that repo”.

1 Like