As I read it, the basic requirements are the same as for
Maven projects with Gradle apparently using your lMaven repository services to resolve dependencies.
So if the JAR in question is a project that you build, then you'd need to build it wuth a "mvn install" (or Gardle equivalent) to build the JAR and post it to your local Maven repository cache. If the JAR is only available in binary form, you'd have to manually catalog it into the Maven repo, which can be done using Maven (here again, there may be a Gradle native equivalent I don't know about).
If the JAR is shared between multiple members of a team, then a site-local Maven repository server such as Nexus can help with that.
The secret of how to be miserable is to constantly expect things are going to happen the way that they are "supposed" to happen.
You can have faith, which carries the understanding that you may be disappointed. Then there's being a willfully-blind idiot, which virtually guarantees it.