I’m using Gradle in one of my Java projects. One of the third party libraries that I’m using in the code has a known bug that will be fixed in the next release. While there is no release I would like to fix it locally. Usually when I wanted to do this in a Maven-based project, I would use classpath override for the buggy 3rd-party class, fix it in my code and then remove this “hack” after the fixed version is release.
For some reason, I’m not able to do this (at least the way I usually did) when running Gradle tasks. Does Gradle use a different classpath order to run the Groovy code and that disables this “feature”?
Does anyone already faced this problem before? Is it possible to do this? How?